On Thu, Feb 20, 2014 at 04:33:39PM +0100, frantisek holop wrote: > the "waf philosophy" is to bundle it with a given project, > to become "part of the project". that is why it does > not "need" to be "package friendly", it is not meant > to be used from a package. if it helps, think of it > as waf == configure and not cmake or such. configure > is also always bundled and nobody cares. > > so the bundled version is the definite version that > should be used. (actually the problematic projects are > the ones that dont bundle it...) > > it takes a bit of getting used to, but i dont see how > it's 'much worse' then megabytes of gnu style shell > code and m4.
It's not really worse, but it's as bad. Any bundled shit like that is bound to be thoroughly untested outside linux/amd64, and hence to break horribly. The only "redeeming" quality of autohell is that we're so used to all the ways it can break that we can generally fix them fairly quickly.
