On Fri, Oct 9, 2009 at 7:43 AM, David Golden xda...@gmail.com wrote:
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)
Comments:
* It's not clear
On Fri, Oct 09, 2009 at 09:38:45AM -0400, David Golden wrote:
On Fri, Oct 9, 2009 at 8:11 AM, Ricardo Signes
perl.cpanw...@rjbs.manxome.org wrote:
* David Golden xda...@gmail.com [2009-10-09T07:42:35]
03. Deprecate YAML Tiny dialect for JSON
Strongly agree.
* I would like one
On Fri, Oct 9, 2009 at 7:54 AM, David Golden xda...@gmail.com wrote:
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. --Chorny 19:40, 21 September 2009 (BST)
On Sat, Oct 31, 2009 at 11:38 AM, Barbie bar...@missbarbell.co.uk wrote:
I see 01, 02 and 03 all part of the same discussion really. There seems
little point in discussing YAML if we think moving to JSON is the better
option. I'm with the strongly agree camp on the first part of above :)
(and
On Fri, Oct 09, 2009 at 08:19:29AM -0400, Ricardo Signes wrote:
* David Golden xda...@gmail.com [2009-10-09T07:47:00]
10. Add a free-text prerequisite field
Strongly oppose. The META file is meant to tell machines about dists. This
will not be useful.
Agreed. This kind of information
On Fri, Oct 09, 2009 at 11:52:50AM -0400, David Golden wrote:
On Fri, Oct 9, 2009 at 7:47 AM, David Golden xda...@gmail.com wrote:
11. OS/arch/platform-specific requirements
Proposal:
I would like to see a way to specify OS-specific requirements. One option
might be to use
On Sat, Oct 31, 2009 at 03:45:31PM -0400, David Golden wrote:
On Sat, Oct 31, 2009 at 2:05 PM, Barbie bar...@missbarbell.co.uk wrote:
Agreed on both counts. type as proposed can be easily derived from the
URLs from the examples. Is there a use case for its use?
Both Subversion, and Git
7 matches
Mail list logo