On Thu, 2001-10-11 at 12:24, Dan Sugalski wrote: > No, we don't have to do it in C. We can do it in perl, we just can't > require perl for the initial build. The steps would be: > > 1) Build minimal perl 6 with default parameters using platform build tool > 2) Run configure with minimal perl 6 > 3) Build full perl 6 with perl build tool and minimal perl > 4) Build full perl 6 distrib with full perl
Did you mean to say perl6 here or parrot? If you meant perl6, then this system cannot be implemented for quite a while. (Note lack of actual language to write in..) > Basically we ship a Makefile and bare-bones config.h, enough to build > miniparrot. Miniparrot then reconfigures itself and builds full parrot, > which then goes and builds the world. Yes - this makes sense - but how does this affect what we want to do now? We don't want to write our buildsystem in parrot bytecode. Replacing the make part of make is easy, with suitable data structures. What are your ideas about "requirements" for the "perl build tool", ignoring the basic stuff that make does (dependencies, etc.) -R
