Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-15 Thread Tim Bunce
On Wed, Apr 14, 2010 at 09:59:32PM -0400, Jesse Vincent wrote: On Wed, Apr 14, 2010 at 09:53:45PM -0400, David Golden wrote: On Wed, Apr 14, 2010 at 8:53 PM, Adam Kennedy a...@ali.as wrote: I've been meaning to propose for a while that for CPAN Perl 5 we drop support for everything

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-15 Thread David Golden
On Thu, Apr 15, 2010 at 10:14 AM, Tim Bunce tim.bu...@pobox.com wrote: On Wed, Apr 14, 2010 at 09:59:32PM -0400, Jesse Vincent wrote: Forcing an extension makes all sorts of tools that previously just worked with a tarball suddenly start to fail. We've dealt with it in the past. However, I'm

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-15 Thread Adam Kennedy
This has already existed for about a year or more. See pip's .p5i file (which I think cpanminus also supports). Adam K On Fri, Apr 16, 2010 at 12:56 AM, Curtis Jewell lists.perl.cpan-work...@csjewell.fastmail.us wrote: Why don't we make the .cpan/.c6pan file (.c6pan) a JSON file, generated by

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-15 Thread Jesse Vincent
Larry points out that the shibboleth for Perl 6 code is: : No package statements. Instead, you'll see module statements. That ought to be a pretty reasonable way for the indexer to know it's Perl 6 code in the absence of other markers. I do think that xdg's plan to have an at-upload-time flag

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-15 Thread Eric Wilhelm
# from Jesse Vincent # on Thursday 15 April 2010 09:24: -1 ... Forcing an extension makes all sorts of tools that previously just worked with a tarball suddenly start to fail. Which tools are going to just work on a perl 6 tarball? If it's a generic tar tool, it should still just work

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-15 Thread Barbie
On Thu, Apr 15, 2010 at 08:56:04AM -0600, Curtis Jewell wrote: wrote: On Thu, Apr 15, 2010 at 10:14 AM, Tim Bunce tim.bu...@pobox.com wrote: On Wed, Apr 14, 2010 at 09:59:32PM -0400, Jesse Vincent wrote: Forcing an extension makes all sorts of tools that previously just worked with a

RE: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-15 Thread Jan Dubois
On Thu, 15 Apr 2010, Barbie wrote: On Thu, Apr 15, 2010 at 08:56:04AM -0600, Curtis Jewell wrote: Why don't we make the .cpan/.c6pan file (.c6pan) a JSON file, generated by PAUSE once the tarball is uploaded, with whatever information is required (a reference to the tarball, what version of

RE: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-15 Thread Jan Dubois
On Thu, 15 Apr 2010, Barbie wrote: On Thu, Apr 15, 2010 at 12:50:29PM -0700, Jan Dubois wrote: PPM4 actually supports putting the PPD file inside the tarball. When the tarball is downloaded with a .ppmx extension, then the client knows to extract the .ppd from inside the file and install

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-15 Thread Adam Kennedy
I'm pretty sure that's true for all such systems, including things like .war files. Even if we split, say, Strawberry from ActivePerl, what if you have multiple installations of ActivePerl? Adam K On Fri, Apr 16, 2010 at 8:56 AM, Jan Dubois j...@activestate.com wrote: On Thu, 15 Apr 2010,

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-14 Thread Ovid
--- On Wed, 14/4/10, Tim Bunce tim.bu...@pobox.com wrote: No need for a radio-box if PAUSE auto-detects from the META file. Tim. Agreed, but you know you're going to see this and variants thereof:     requires:         perl: 6,0 Should that be a rejection for unknown format? I would

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-14 Thread Graham Barr
On Apr 14, 2010, at 6:48 AM, Tim Bunce wrote: If we separate Perl 5 and Perl 6 distributions within the file system, we can distinguish between them easily and without relying on indexes, meta data files or other elements of complexity. True, but is that *really* a significant need? Why

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-14 Thread Elaine Ashton
On Apr 14, 2010, at 8:55 AM, Graham Barr wrote: On Apr 14, 2010, at 6:48 AM, Tim Bunce wrote: If we separate Perl 5 and Perl 6 distributions within the file system, we can distinguish between them easily and without relying on indexes, meta data files or other elements of complexity.

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-14 Thread Ricardo Signes
* Adam Kennedy a...@ali.as [2010-04-14T20:53:15] Alternative option, when we switch to Perl 6 also take the opportunity to switch to a specific named extension. D/DA/DAGOLDEN/Foo-Bar-1.23.c6z I haven't wanted to get into this thread, but I will say that I had the same idea as Adam, and

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-14 Thread David Golden
On Wed, Apr 14, 2010 at 8:53 PM, Adam Kennedy a...@ali.as wrote: I've been meaning to propose for a while that for CPAN Perl 5 we drop support for everything other than tar.gz (we can talk about the need for zip files later) and encourage a switch to something like

How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-13 Thread David Golden
I'm writing up my notes from an extensive IRC conversation with Jesse Vincent. I offered to post it to cpan-workers for feedback. He and I agree that there are significant benefits to the community to using a single repository for both Perl 5 and Perl 6 distributions. We worked through some

Re: How to have Perl 5 and Perl 6 cohabitate nicely on CPAN

2010-04-13 Thread Eric Wilhelm
# from David Golden # on Tuesday 13 April 2010 10:48: Our proposal is for Perl 6 modules to be uploaded into a 'perl6' subdirectory of a CPAN author's directory like so:   ...D/DA/DAGOLDEN/perl6/Foo-Bar-1.23.tar.gz This would require changes to any tools which think that D/DA/DAGOLDEN/*/ are