Perl > cpan-workers > October 2009

17. Better formalization of license field Proposal: Replace the list of strings for the "license" field with something extensible and unambiguous. (RicardoSignes) Comments: * I believe Module::Build ...

19. Make repository resource a hash [Note, a separate "Make repository more machine readable" proposal has been merged into this one.] Proposal: Currently we have a simple URL for the repository ...

06. Data structures, not YAML Proposal: The META spec should be defined in terms of (Perl) data structures, and not in terms of YAML. (Slaven Rezic) Comments: * This does not mean that I want to ...

30. Trove-Like Categories Proposal: Add Freshmeat.net or SourceForge-like trove categories with topics programming languages, etc. As opposed to keywords/labels/tags they are a nested tree, and will ...

22. Clarify author field Proposal: I would like to see some clarification of what an author is, especially since the numbers of distros * that change ownership * that use collaboration * that use ...

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 to reuse the ...

21. Formalize optional_features Proposal: 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. ...

33. Install Meta files and make them queryable Proposal: Using something like .packlist or File::ShareDir, the Meta file should be installed along with the distribution and Meta tools should allow ...

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 extensions that we ...

26. Specify a DLSIP resource Proposal: DLSIP codes should be specified in META.* as a resource. Comments: * search.cpan.org has a URL that resolves and describes the DLSIP coding. I am suggesting ...

16. Binary Package Dependencies Proposal: Add a binary dependency keyword to be optionally resolved by the shell. eg. binary_requires: - linux-debian: libgif4-dev: 4.1.6 - linux-ubuntu: libgif4-dev: ...

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. ...

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 ...

12. Allow Sequences (Arrays) for Prereqs Proposal: Right now, to the best of my knowledge, the only benefit of a the magic "Bundle::" namespace is that its prerequisites can be declared in optimal ...

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 ...

07. Enhance granularity of prerequisites Proposal: Add "test_requires" distinct from "build_requires". (Adam Kennedy) This proposal is driven by the needs of the downstream distribution packagers. At ...

20. Make bugtracker resource a hash Proposal: The bugtracker resource shoudl be made into a hash that defines different types of resources, e.g. web page, email report address, etc. (#toolchain ...

10. Add a free-text prerequisite field Proposal: Add free-text entries that *describe* prerequisites that cannot be described right now, like "prerequisite: a working libexpat", "Need a perl with ...

05. Schema Proposal: The META spec should come along with a formal schema definition. (SlavenRezic) Comments: * There are at least two schema languages available for this task, both with a Perl ...

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 Devel::CheckOS, which already seems to have a ...

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: * ...

03. Deprecate YAML Tiny dialect for JSON Proposal: The current META.yml isn't really YAML. It has many of the drawbacks of YAML and none of the technical benefits. It has the benefit of being sort of ...

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 ...

31. Version changes Proposal: Description of changes in that versions and tags for changes. Useful for submission to Freshmeat and for quick review of changes. --Chorny 18:51, 30 September 2009 (BST)

25. Controlling test suite runs Proposal: The META spec should add flags to indicate that distribution's tests may be shuffled or run in parallel. (SlavenRezic) Comments: * The prove utility provides ...

08. Extensibly Group Prereqs Proposal: Rather than have 'config_requires' and 'install_requires' and 'signature_requires' and 'build_recommends', have a two-level system. This requires a small bit of ...

18. Make dynamic_config mandatory Proposal: Make the 'dynamic_config' a mandatory field (Dagolden) Comments: * dynamic_config is confusing because if missing, it defaults to 1. Further, the default ...

23. Have a "development version" flag Proposal: Add a boolean value indicating whether the release is a "production" or "alpha/developer/beta/whatever" release. [[User:elliot|Elliot Shank]] Comments: ...

14. Prerequisites should be mutually exclusive Proposal: Modules should only be listed once across all prerequisite categories. E.g. a 'requires' module shouldn't be listed in 'test_requires'; a ...

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 ...

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 dist to Ohloh, ...

01. Update the YAML version declaration Proposal: The version declaration for YAML has not been "--- #YAML:1.0" for a long time, update it to the current YAML 1.1 equivalent.

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 ...

32. Steal from other package meta specs Proposal: Hunt down the spec authors and some heavy package users, ask what in the spec/package meta files works for them and what doesn't, then steal the best ...

24. Add a "release_status" field Proposal: Add a mandatory ''release_status'' field with a limited list of acceptable values. E.g. "stable", "testing" and "unstable", with "alpha" as an alias for ...

I've updated the summary since Oct 10 and noted where patches have been offered. #--------------------------------------------------------------------------# Formatting and Schema 01. Update the YAML ...

On November 1, I'm going to declare the public comment period over. That means I'll take areas of consensus and corresponding patches and merge them into a proposed draft spec. For anything with ...

Thank you to everyone who has commented so far. I'm very pleased that within 24 hours, we seem to have an emerging consensus (agreeing or opposing) on most proposals. For each proposal listed below, ...

Rick volunteered to restructure the spec file to create sections for data structures versus serialization method and to convert the examples from YAML to Perl data structures. This is a great base to ...

I would say so, and it's a better solution, too. +1 --Curtis -- Curtis Jewell swordsman@csjewell.fastmail.us %DCL-E-MEM-BAD, bad memory -VMS-F-PDGERS, pudding between the ears [I use PC-Alpine, which ...

Here is the list of 34 proposals, grouped by category. Individual emails for each proposal will follow. (Two near identical proposals were merged). In some cases, particularly the "Formatting and ...

[Apologies for getting this note out a week after closing the CFP. I underestimated the effects of 12 hours of jet lag on my productivity.] Dear CPAN workers and CPAN Meta Spec working group, I'm ...