It seems to me that we should look at cons before writing Yet Another Perl Build System. (i haven't used it myself, so I don;'t know if it's good or not). For reference: http://www.dsmit.com/cons/
--Josh At 12:18 on 10/11/2001 PDT, Robert Spier <[EMAIL PROTECTED]> wrote: > > | I'm OK requiring a C compiler and a build tool for a platform. It's a C > | compiler and perl 5 that I don't want to require. (Rather nasty > | bootstrapping issues there... :) > > This makes things a lot harder. Suddenly we're > re-implementing make. (in C) > > Speaking of re-implementing make, I just finished cranking > out a really simple make-alike in perl. It uses essentially > the same syntax, but has no frills. > > Frills = parallel building, implicit rules, variables. > > Most of these frills are "in progress". > > But - if perl5 is going to be a nono - then this isn't going > to be an option. > > Would it make sense to start with something like this and > re-evaluate it when python/perl6 has matured so that it can > bootstrap its own build process? > > -R
