Re: Perl 6 versus the CPAN

2010-01-05 Thread Steffen Mueller
Hi David, hi all, David Golden wrote: Except that we're in feature freeze for Perl 5.12, so that won't actually happen until 5.13. But as soon as Perl 5.12.0 ships, I plan to pull the trigger on JSON and HTTP::Lite and make them CPAN.pm dependencies so we can (a) bootstrap CPAN with HTTP and

Re: Perl 6 versus the CPAN

2010-01-05 Thread brian d foy
In article 5d4beb41001041958q3b5d9219gac4360cfc8c2d...@mail.gmail.com, David Golden xda...@gmail.com wrote: On Mon, Jan 4, 2010 at 5:15 PM, brian d foy brian.d@gmail.com wrote: Yikes. How about we move away from text files and towards structured data like JSON. When JSON is core that

Re: Perl 6 versus the CPAN

2010-01-04 Thread Ovid
--- On Mon, 4/1/10, Eric Wilhelm enoba...@gmail.com wrote: From: Eric Wilhelm enoba...@gmail.com If Parrot itself supports trans-language calls (which I'm led to understand it can?) then a single index gives us the potentially huge win of cross-language dependencies. Does it?  Tell me

Re: Perl 6 versus the CPAN

2010-01-04 Thread Eric Wilhelm
# from Zefram # on Monday 04 January 2010 03:23:  use perl5:Text::Wrap 'wrap'; That would seem to settle it, then: perl5:Config::INI does not conflict with perl6:Config::INI. I believe that's supposed to be use Text::Wrap:fromperl5. But yes it's a different set of namespaces. --Eric --

Re: Perl 6 versus the CPAN

2010-01-04 Thread Geoffrey Broadwell
(I had a big response going to various details of this thread, and then realized that from Plumage's perspective, the details don't actually matter much; see the more general email below.) On Mon, 2010-01-04 at 10:45 -0500, Jesse Vincent wrote: This brings us to How do we get there from here?

Re: Perl 6 versus the CPAN

2010-01-04 Thread Adam Kennedy
It's been something of a long-standing (second-order) problem that packages are just tarballs (or bzipball, or zips, etc). The lack of a standard file extension means that we can't sanely implement features like double-click to install on operating systems and browsers with file extension

Re: Perl 6 versus the CPAN

2010-01-04 Thread Adam Kennedy
I'd rather like to avoid adding additional complexity to the current index files. Instead, what about switching to a native SQLite index for the new system. This is working quite nicely in the JSAN now, and it greatly simplifies things because you can download the index much more simply. 1.

Re: Perl 6 versus the CPAN

2010-01-04 Thread Eric Wilhelm
# from Adam Kennedy # on Monday 04 January 2010 16:07: I'd rather like to avoid adding additional complexity to the current index files. ... This would, of course, mean that SQLite and DBI support is needed in ... the modules needed to install other modules ... ^

Re: Perl 6 versus the CPAN

2010-01-04 Thread David Golden
On Mon, Jan 4, 2010 at 5:15 PM, brian d foy brian.d@gmail.com wrote: 02packages is actually quite flexible. There's a line in the header that tells consumers what the columns are. Since we've used the same three columns, a lot of stuff has assumed that the order and meaning will always be

Re: Perl 6 versus the CPAN

2010-01-03 Thread Eric Wilhelm
# from David E. Wheeler # on Sunday 03 January 2010 19:20: FYI: http://gitorious.org/parrot-plumage http://irclog.perlgeek.de/perl6/2010-01-04#i_1883152 http://perlcabal.org/syn/S11.html#Versioning http://trac.parrot.org/parrot/wiki/ModuleEcosystem --Eric -- It is impossible to make