On Thu, Oct 30, 2008 at 7:18 AM, Bill Ward [EMAIL PROTECTED] wrote:
I think supporting options like other or mixed should resolve most
of these cases. Sure, automatic tools that use this field will be out
of luck, but that should be a fairly small minority.
This is exactly what I mean.
I
I guess I can do that, but I think having a 1 liner BUILD subroutine
is simpler than writing an extension to Config::Any.
I'm afraid of starting a YAML vs. The World flamewar, but I don't like
YAML since it differs between white space and tab-created whitespace
and a few other small nuisances
On Wed, Oct 29, 2008 at 11:13:24PM -0500, Ken Williams wrote:
On Mon, Oct 27, 2008 at 11:17 AM, David Cantrell [EMAIL PROTECTED] wrote:
So, in summary, here's my objections to the
current 'license' field in META.yml:
* poorly documented;
* limited range of options for licences;
* only
* David Cantrell [EMAIL PROTECTED] [2008-10-30T12:53:58]
I agree that the second point is a problem. I'd like to solve it by
delegating to Software::License. Anything it knows about should be a
valid choice.
All that does it make it Someone Elses Problem while still not solving
the
