>python is far harder to use than bash when it comes to running processes and doing things with them and doing the file-system manipulation that is usually want

>python is far harder to use than bash when it comes to running processes and doing things with them and doing the file-system manipulation that is usually wanted when building. Can easily be solved by having libraries that does. Which is far better solution that hacking/chaining 5 different obscure unix tools to do string manipulation. >you can introduce all sorts of ordering problems when a build runs on a different machine and doesn't work because it's executing build tasks in a different order. Surely it is better than make? Even if make is "better" because it "just works". This is basically Hyrum's Rule waiting to be unleashed. >If you really want to build by "writing a script" (groan - because that's the age old horrible solution) why bother with python? Because I personally cannot decipher make and I think this is the experience of many developers as well. And how many make derivations are there? Its basically an arcane spell that needs to be chanted with every project (configure -> make -> make install).