David Golden wrote:
On Fri, Oct 9, 2009 at 9:31 AM, Graham Barr wrote:
On Oct 9, 2009, at 6:43 AM, David Golden wrote:
05. Schema
Proposal:
The META spec should come along with a formal schema definition.
(SlavenRezic)
I am not so much concerned about a formal schema. But an official modul
egards,
Slaven
On Fri, Oct 9, 2009 at 8:14 AM, Ricardo Signes
wrote:
* David Golden [2009-10-09T07:44:43]
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)
Agreed, but the spec should b
David Golden wrote:
On Sun, Nov 1, 2009 at 3:51 AM, Slaven Rezic wrote:
- those who don't care to eval perl code, because they do it anyway in the
same process (i.e. when installing a CPAN distribution with CPAN/CPANPLUS)
The second group doesn't really want to do it either in
David Golden 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 Devel::CheckOS, which already seems to have a comprehensive
list of supported OS names, and have a hash like:
os_requires:
Linu
David Golden wrote:
16. Binary Package Dependencies
-1
However, I like the idea of a data structure describing external
dependencies. But I would like to locate this into a generic Alien
interface/driver module family. This one knows about
OS/distribution-specific installation procedures (y
David Golden wrote:
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 contained in the
resources/repository key. It would be good if more informatio
David Golden wrote:
On Fri, Oct 9, 2009 at 7:51 AM, David Golden wrote:
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. (Tux)
I'm for doing som
Jan Dubois wrote:
On Fri, 09 Oct 2009, David Golden wrote:
Though to be fair, "author" is currently *required*, and I like the
idea that there be a required point of contact. However, I don't like
the idea of a mandatory "resources" field.
How about if it gets renamed "auth" and the description
David Golden wrote:
On Fri, Oct 9, 2009 at 7:56 AM, David Golden wrote:
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
easy querying of meta inf
David Golden wrote:
On Sun, Nov 1, 2009 at 2:01 PM, Slaven Rezic wrote:
"url" is not enough to describe how to checkout from a CVS repository. At
least username and password (for "cvs login") and url and module (for "cvs
-d url co module") are needed.
Can you g
David Golden wrote:
On Sun, Nov 1, 2009 at 10:51 AM, Slaven Rezic wrote:
Why not? A few CPU cycles later "perl Makefile.PL" or "perl Build.PL"
happens.
Yes, but in a subprocess.
Where's the difference? There's no extra security CPAN.pm provided when
executing
Adam Kennedy wrote:
I still think I prefer Zefram's approach, remove optional_features entirely.
I would rather get rid of "suggests" and "recommends". optional_features
is not that different from these both, but it has a name and a
description. I'd rather pick the feature "fulltext_search" t
David Cantrell wrote:
On Sun, Nov 01, 2009 at 08:01:50PM +0100, Slaven Rezic wrote:
David Golden wrote:
resources:
repository:
web: http://github.com/2shortplanks/test-time-hires
url: git://github.com/2shortplanks/test-time-hires.git
format: git
type: github
Slaven Rezic wrote:
David Golden wrote:
On Sun, Nov 1, 2009 at 2:01 PM, Slaven Rezic wrote:
"url" is not enough to describe how to checkout from a CVS
repository. At
least username and password (for "cvs login") and url and module
(for "cvs
-d url co module"
14 matches
Mail list logo
