On Wed, Jan 18, 2006 at 12:10:34PM -0800, jerry gay wrote: > true, but i think DRY (don't repeat yourself) applies here. there's > already a standard repository for these modules, so why clutter the > parrot repo?
Yes. Those who do not understand CPAN, etc. There should be a single CPAN bundle which, when installed, will pick up everything that a Parrot developer/tester requires. If you want to go the extra mile and create sub-bundles for other purposes, like testing-only, that's OK too. But unless the testers complain about having more Damian code sitting on their hard drive, I don't see any point in distinguishing dev from test. I envision a "fat parrot" tarball which includes not only the basic "thin parrot", but also required non-standard Perl modules, ICU, and other dependencies that a bare Unix system would not have. That should meet the needs of those who can't easily access the net during installation. That takes care of the tarball policies. Any system with a customized installer system will impose its own policies and practices on the developer who's foolhardy^Wbrave enough to package Parrot, so there's no point in me trying to dictate anything for them. -- Chip Salzenberg <[EMAIL PROTECTED]>
