Yeah, I wouldn't be surprised if instead of switching back to plain text logs, they switched to using an sqlite db ... one more small dependency to keep adding on to the vast list of small dependencies.
They used xml to allow for processes to have multiple children, but xml only allows 1 parent per child, so it cannot effectively address a process that requires completion of multiple events simultaneaously. ... but guess what? this is easily done in a shell script like this (simplified) script:
Code: Select all
parentA(){
dostuff
}
parentB(){
domorestuff
}
childofAB(){
finishstuff
}
#this could be a function as well if necessary
parentA &
A=$!
parentB &
B=$!
wait $A $B
childofAB
pseudo xml this would look like:
Code: Select all
<dummy parallelchildren="true">
<parentA>dostuff</parentA>
<parentB>domorestuff</parentB>
</dummy>
<childAB>finishstuff</childAB>
but adding extra non-dependent processes becomes trickier
One way would be to have a separate project manager that accounts for each process's predecessor/successor and resource usage to organize the workflow. Existing project managers (planner, etc...) are not designed for this, but I could probably put one together in js to output optimized shell script ... I could even add comments to denote misuse of sed,cut,tr,grep,awk,etc... where shell builtins would be faster.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].