At this point in the development cycle you can certainly make such arguments (although I would tend to fall on the side of consistency myself, at least for things that really Don't Matter in the grand scheme of things, such as POD modules).
But once we start expecting people in the real world to compile this thing on their boxes in order to install perl, it would be extremely foolish to make them manually download and install perl6 + parrot + icu + perl5 + cpan modules 1 through 10, all from different sources. IMHO, the releases better include everything necessary to build the application, within reason. Consistency and simplicity counts for a lot. Why create headaches we don't need? The development environment can of course be more fluid. --Josh At 15:05 on 03/04/2004 PST, Robert Spier <[EMAIL PROTECTED]> wrote: > > The determinism seems perhaps worth the bloat. It's quite localize > > bloat after all. > > I disagree. > > We _want_ a heterogeneous environment -- a homogeneous environment > doesn't exist in the real world -- most of your concerns were with > tracking down the issues. Since we have parrotbug now (or real soon) > we can take a better snapshot of whats going on. > > If we want to require certain versions, that becomes a problem ot some > people. But we can do it by providing URL's to where people can > download the specific versions and instructions on how to set that up > for parrot's use only. But we don't need to bundle it _with_ Parrot. > > -R
