On Fri, Aug 22, 2003 at 06:04:14PM -0400, James E Keenan wrote: > If module authors are expected to provide META.yaml files with their > distributions, then that technology should be mature and tested enough that > it can be included/recommended in the documentation such as 'perlnewmod'.
I have this hunch that an important point is being missed here: You don't write the META.yml out yourself. Module::Build or ExtUtils::MakeMaker does it for you when you make a dist. You only need to care about the spec if you intend to generate or parse the file. If you're generating it then you're probably reinventing distribution packaging, in which case you've probably got bigger problems than worrying about a new file to ship. > When I wrote my modules I followed those instructions scrupulously, and > because the current technology is well-tested, no one has ever had a problem > with uploading or downloading them. Before I adopt a new procedure, I want > to know it's solid. Then, I'll follow it down the line. Your new procedure is 1) upgrade your ExtUtils::MakeMaker[0] to 6.16 or newer 2) add META.yml to your MANIFEST 3) Profit META.yml isn't meant to be a burden on authors, just a tool for people who want at the metadata without having to parse/run your code. Hope this helps. [0] I'm assuming ExtUtils::MakeMaker if you have existing code, for new modules I suggest people use Module::Build and look at the create_makefile_pl option if you have compatibility concerns. -- Richard Clamp <[EMAIL PROTECTED]>
