Re: sponsor logo on home of CPAN mirror

2018-01-01 Thread Graham Barr
> On Dec 31, 2017, at 07:25, Henk P. Penning wrote: > > > I don't see how such a change can be kept local ; > how can it /not/ propagate to downstream mirrors? If the JSON file was named using the mirror hostname then index.html can extract the name from the URL and it

Re: Adjusting CPAN::Mirrors to make it more useful

2011-04-28 Thread Graham Barr
On Apr 28, 2011, at 11:19 , brian d foy wrote: On Tue, Feb 8, 2011 at 4:44 AM, Adam Kennedy a...@ali.as wrote: I think I may have implemented what you're looking for several years ago for JSAN, which has a client that auto-detected appropriate mirrors in a few seconds each time it starts.

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: Trimming the CPAN - Automatic Purging

2010-03-25 Thread Graham Barr
On Mar 25, 2010, at 8:42 AM, Barbie wrote: Lastly I would also personnally be annoyed if only the latest versions were available, as I often make great use of the diff tool on search.cpan.org. Having only the latest version renders that great tool redundant :( I use that too :-) and it is

Re: CMSP 02. Formally switch to YAML Tiny

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 7:11 AM, Ricardo Signes wrote: * David Golden xda...@gmail.com [2009-10-09T07:42:06] 02. Formally switch to YAML Tiny Proposal: Change the language referring to YAML to instead refer to YAML Tiny and update the specification URL to point to the YAML Tiny specification.

Re: CMSP 03. Deprecate YAML Tiny dialect for JSON

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 7:11 AM, Ricardo Signes wrote: * David Golden xda...@gmail.com [2009-10-09T07:42:35] 03. Deprecate YAML Tiny dialect for JSON Strongly agree. * I would like one violation of the JSON spec: allow Javascript-style comments. My one beef with the JSON spec. Elliot

Re: CMSP 04. Formalize allowed version number formats

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 7:12 AM, Ricardo Signes wrote: * David Golden xda...@gmail.com [2009-10-09T07:43:00] 04. Formalize allowed version number formats Proposal: Formalize the spec for version numbers as decimal or normalized dotted-integer (leading v and at least 3 components). (Dagolden)

Re: CMSP 09. Clarify intent of 'recommends' and add 'suggests'

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 6:46 AM, David Golden wrote: 09. Clarify intent of 'recommends' and add 'suggests' Proposal: The 'recommends' flag is not equivalent to Debian recommends. The intent should be made clear for authors and the toolchain. If the Debian definitions are adopted to better

Re: CMSP 13. Add a post_depends set

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 6:48 AM, David Golden wrote: 13. Add a post_depends set Proposal: Permit specifying of packages that should be installed to provide part of a packages functionality, but should be installed/built *after* the package is installed. (kentnl) I hate circular

Re: CMSP 15. Add development_requires

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 6:49 AM, David Golden wrote: 15. Add development_requires Proposal: The development_requires field should specify all prerequisites only needed during development. For example this could include templating or other preprocessing modules needed to generate the final

Re: CMSP 16. Binary Package Dependencies

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 8:12 AM, Ricardo Signes wrote: * David Golden xda...@gmail.com [2009-10-09T07:49:40] 16. Binary Package Dependencies No vote, but highly dubious that it could be done in a way we won't regret later. I agree. Graham.

Re: CMSP 17. Better formalization of license field

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 6:50 AM, David Golden wrote: 17. Better formalization of license field Proposal: Replace the list of strings for the license field with something extensible and unambiguous. (RicardoSignes) +1 From the perspective of search.cpan I would like to see it have two

Re: CMSP 27. Long description

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 8:18 AM, Ricardo Signes wrote: * David Golden xda...@gmail.com [2009-10-09T07:54:13] 27. Long description Proposal: Field for long description that can be used in search, when generating README, OS packages or submitting dist to Ohloh, Freshmeat and similar sites.

Re: CMSP 28. Short description

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 8:19 AM, Ricardo Signes wrote: * David Golden xda...@gmail.com [2009-10-09T07:54:35] 28. Short description Proposal: Field for short description that can be used in search (with higher priority than long description), when generating README, OS packages or submitting

Re: CMSP 29. Language

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 8:19 AM, Ricardo Signes wrote: * David Golden xda...@gmail.com [2009-10-09T07:54:51] 29. Language Proposal: 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

Re: CMSP 34. Formally reserve keys for private 'in-house' use

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 8:20 AM, Ricardo Signes wrote: * David Golden xda...@gmail.com [2009-10-09T07:56:46] 34. Formally reserve keys for private 'in-house' use Proposal: For in-house, non-CPAN use, it would be nice to be able to extend META.yml to contain extra keys and data, but any

Re: CMSP 17. Better formalization of license field

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 11:53 AM, Ruslan Zakirov wrote: * There won't need to be a list, apart from perhaps 02packages. also, cpan:///package/Software::License::Perl_5 works; it makes it easy to re-use your own license in a machine-readable way by publishing it as a package, and is

Re: CMSP 06. Data structures, not YAML

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 9:11 AM, Jarkko Hietaniemi wrote: I really don't think we should have Perl data structures in files (that means Perl code, right?), because that indicates doing an eval, and I don't want to eval any more random code off the 'net than necessary. I strongly agree that we

Re: CMSP 19. Make repository resource a hash

2009-10-09 Thread Graham Barr
On Oct 9, 2009, at 3:21 PM, David Golden wrote: On Fri, Oct 9, 2009 at 7:51 AM, David Golden xda...@gmail.com wrote: 19. Make repository resource a hash resources: repository: web: http://github.com/2shortplanks/test-time-hires url:

Re: CPAN meeting minutes

2001-09-05 Thread Graham Barr
On Fri, Jun 29, 2001 at 06:43:13PM -0400, Chris Nandor wrote: At 08:36 -0400 2001.06.24, Jon Orwant wrote: On Sun, Jun 24, 2001 at 12:28:06AM -0700, Ask Bjoern Hansen wrote: On Sat, 23 Jun 2001, Elaine -HFB- Ashton wrote: btw - Is there anything we can do at TPC for Paul 'the testing