First, I'd like to address people's concern over the format of the META
file. Module users and 99% of module authors have nothing to be concerned
about. Most folks shouldn't even know the thing exists.
Module::Build has been generating and using META.yml since nearly the
beginning.
On Wed, 12 Nov 2003, Sam Vilain wrote:
On Tue, 11 Nov 2003 02:29, Michael G Schwern wrote;
YAML was chosen because its human readable and writable, its data
^ ^
So long as you're a FREAK who likes INDENTING and WHITESPACE to
OK, maybe I'm missing a LOT of context here, 'cause I haven't been
agressively keeping up with this mailing list, but the security hole
argument seems a bit odd.
These META.yml files we're refering to -- these are meta data for
managing the build process, files that will be distributed along
Chris == Christopher Hicks [EMAIL PROTECTED] writes:
So, if I understand this correctly, you're worried about the build
process eval'ing the contents of a file I sent you. Hmm.
OK, why is that anymore of a concern for eval'ing the perl module I
also distributed, too? Isn't that just as
On Wed, Nov 12, 2003 at 04:11:45PM +, Sam Vilain wrote:
On Tue, 11 Nov 2003 02:29, Michael G Schwern wrote;
YAML was chosen because its human readable and writable, its data
^ ^
So long as you're a FREAK who likes INDENTING and
On Mon, Nov 10, 2003 at 05:42:03PM -0800, Terrence Brannon wrote:
Thinking more about this, I guess META.yml would need to provide a
little more info to a configure module. Would something like the
following work?
It's probably too late, but I am not keen on YAML. What is wrong with
pure
