Improved output for recursive invocations
hyperupcall opened this issue · 1 comments
hyperupcall commented
Given the following Bakefile.sh
...
task.default() {
./bake package && ./bake link
}
task.package() {
bake.assert_cmd 'zip'
zip --recurse-paths --exclude='.git/*' --exclude='out/*' './out/foxxy.sublime-package' .
}
task.link() {
ln -fs ./out/foxxy.sublime-package "${XDG_CONFIG_HOME:-"$HOME/.config"}/sublime-text-3/Installed Packages/Local Sublime Text Foxxy"
}
Doing bake defualt
yields the following...
> bake default
-> RUNNING TASK 'default' ==================================================================================================================================================================
-> RUNNING TASK 'package' ==================================================================================================================================================================
updating: README.md (deflated 36%)
updating: editorconfig.sublime-snippet (deflated 55%)
updating: Bakefile.sh (deflated 34%)
updating: .gitignore (stored 0%)
updating: bake (deflated 64%)
<- DONE ====================================================================================================================================================================================
-> RUNNING TASK 'link' =====================================================================================================================================================================
<- DONE ====================================================================================================================================================================================
<- DONE ====================================================================================================================================================================================
This could be better
hyperupcall commented
Meme issue, task.package && task.link
is the clear solution. This tool shouldn't "support" recursive invocations like Make
, etc.