Re: CMSP 21. Formalize optional_features

2009-10-11 Thread Zefram
David Golden wrote: Optional features: is supported in META.yml, but it requires a lot of manual intervention and trickery to make it work. And it is very poorly documented. (Tux) Get rid of it. I think each such feature should be reified as a module, which one can declare as a dependency of

Re: CMSP 17. Better formalization of license field

2009-10-11 Thread Zefram
David Golden wrote: 17.01) Enumerate a list of license strings explicitly in the spec, Yes, that's good. 17.02) Make the license field an arrayref rather than a scalar. Bad idea as it stands. There are at least two ways that different licenses can be combined in one distro: (a) you may

Re: CMSP 26. Specify a DLSIP resource

2009-10-11 Thread Zefram
David Golden wrote: DLSIP codes should be specified in META.* as a resource. No. DLSIP was an early attempt at metadata, and should be superseded by META. It is not a single piece of information, but an abbreviated representation of five separate items. The P item is already covered by META.

Re: CMSP 17. Better formalization of license field

2009-10-11 Thread David Golden
On Sun, Oct 11, 2009 at 3:21 AM, Zefram zef...@fysh.org wrote: 17.02) Make the license field an arrayref rather than a scalar. Could make the field a string expression, with the defined keywords as atomic expressions, | and operators for license combination, and parens for precedence.  A

Re: CMSP 29. Language

2009-10-11 Thread Zefram
David Golden wrote: Perl 6 is coming. Some code in Perl 6 is already being uploaded to the CPAN. A new language field is an important part of the structure we need to allow Perl 6 to reuse the existing CPAN We certainly need something in this direction. We should be clear that each language has

ENOMAIL

2009-10-11 Thread Barbie
Anyone any idea why I'm not getting mail to this list? Have I been blocked? Nothing in my spam traps and the last mail i got was Aug 26. I note that there has been a flurry of CMSP items in the web archives, but I'm not going to both cut-n-pasting replies to into emails :( Cheers, Barbie. --

Re: ENOMAIL

2009-10-11 Thread David Golden
On Sun, Oct 11, 2009 at 4:08 PM, Barbie bar...@missbarbell.co.uk wrote: Anyone any idea why I'm not getting mail to this list? Have I been blocked? Nothing in my spam traps and the last mail i got was Aug 26. I note that there has been a flurry of CMSP items in the web archives, but I'm not

Re: CMSP 17. Better formalization of license field

2009-10-11 Thread Ricardo Signes
* David Golden xda...@gmail.com [2009-10-11T21:49:28] On Sun, Oct 11, 2009 at 8:59 PM, Ricardo Signes perl.cpanw...@rjbs.manxome.org wrote: I am also happy to add a meta2_name method to all the Software::License classes to avoid a direct connection between SL and META, but I don't want to

Re: CMSP 17. Better formalization of license field

2009-10-11 Thread Chris Weyl
On Sun, Oct 11, 2009 at 5:10 PM, David Golden xda...@gmail.com wrote: On Sun, Oct 11, 2009 at 5:33 PM, Chris Weyl chris.w...@gmail.com wrote: we ought to give authors a clear, easy way to unambiguously specify the terms their software is under... Authors have a clear, easy, unambiguous way

Re: CMSP 17. Better formalization of license field

2009-10-11 Thread David Golden
On Sun, Oct 11, 2009 at 11:15 PM, Chris Weyl chris.w...@gmail.com wrote: As a packager outside of the CPAN I want to have a good idea if we can redistribute the software -- legally and within project policy.  Just as dependency metadata gives me a good view into the software's requirements, so

Re: CMSP 29. Language

2009-10-11 Thread Tim Bunce
On Sun, Oct 11, 2009 at 01:44:16PM -0400, Jarkko Hietaniemi wrote: Zefram wrote: David Golden wrote: Perl 6 is coming. Some code in Perl 6 is already being uploaded to the CPAN. A new language field is an important part of the structure we need to allow Perl 6 to reuse the existing CPAN