yaml dep in g-cpan: Objections?

I'm thinking of forcing a dep on dev-perl/yaml in the next release of
g-cpan. (Assuming all goes well) I've been working on the dep check code
this morning, and it appears to be working great, but a portion of it
relies on yaml (in the presence of a META.yml file of course). Anyone
think of any objections to this? KEYWORD wise the only 'problem' I see
is that g-cpan has been keyworded for the alt-arch's (the porting
portage archs, not native linux arch's), but that's really only a
problem until I file a keywording bug. I'm going to keep coding on the
assumption that there are no objections, but let me know (on or off
list) if you can think of a valid reason not to include it as a dep.
Thanks all!

~mcummings, attempting to boost this lists mail flow to 3 messages this
week

pgpV9SLvCVNIo.pgp
Description: PGP signature