On Sat, Mar 05, 2005 at 03:25:55PM -0800, Darren Duncan wrote: > I wish to help out the development of Perl 6, initially running under > Pugs, by supplying test code of sorts, written in Perl 6, that we > would attempt to run under Pugs (and eventually Parrot) to ensure > that it works correctly with the subset of Perl 6 that I use.
Wonderful! :-) As Stevan has answered your quetions quite well, I'd only take Q4: > Question 4: If Perl 6 code is to start being released to CPAN now, is > there an already planned method for those distros to say the right > things in their Makefile.PL so that the existing automated CPAN > testers network can know to run them through Pugs? Or do we just > have to skip automated tests for now? We at #perl6 had brainstormed on that question today; see my journal for a writeup: http://use.perl.org/~autrijus/journal/23524 Basically, to avoid disrupting CPAN in general, and consider Pugs' current immaturity in supporting the P6 module spec (with "long names" and advaced versioning), it is recommended that you commit your modules work under the Pugs tree's ext/Locale-KeyedText/ directory for now. If that sounds okay with you, I'll send you an invitation mail for you to become a committer. Eventually we need to figure out a way to distribute P6 modules either as a prefixed distname on CPAN (using Module::Install::Perl6 to correctly run tests with pugs/perl6 and install into the correct path), adopting either the Perl6-lib-* prefix or the shorter p6-* prefix; another possibility is to set up a dedicated CPAN subdirectory to host P6 modules. This all needs some discussion with CPAN workers and Perl 6 design team, and until that is settled, committing into the Pugs tree sounds like the safest bet. I'll update the Apocrypha after some more discussion on #perl6 and a better-worded consensus is reached. :) Thanks, /Autrijus/
pgpj0GhVGA1mh.pgp
Description: PGP signature
