On Saturday 18 October 2003 02:20 CET Michael G Schwern wrote:
Yes, it should be overwritten by default because most projects shouldn't even know its there. Part of the reason for slipping META.yml generation quietly into MakeMaker was to rapidly populate CPAN with meta information without making all the CPAN authors aware of it and having them all add a new flag to their module. Now it just happens the next time they upload a new version of their module with a recent MakeMaker.
But you can't get around noticing META.yml if the developer use CVS in combination with different versions of EU::MM.
I had that problem with the SpamAssassin Makefile.PL: Processed it with a newer EU::MM and META.yml got added to the MANIFEST; accidently checked in that MANIFEST, another dev got errors because that file was missing for him. Tried to check in META.yml but noticed that it will change everytime somebody processes Makefile.PL so that file got a real annoyance, CVS-wise.
In the end I just went the easy way and added NO_META. Oh, not really easy, had to add a workaround and remove that key on old EU::MMs again because else users get spurious warnings [1]... *sigh*
Cheers, Malte
[1]http://bugzilla.spamassassin.org/show_bug.cgi?id=2434
Yes, I have thought of this too. Michael, you say that you wanted to add this new feature in a "stealth" manner, but the modification of MANIFEST is what makes it visible.
One possible workaround is not to include META.yml in MANIFEST, but let MM add it on the fly after reading MANIFEST if it's found in the root directory and wasn't already listed in MANIFEST (which folks will do on their own will, usually when they want to maintain it themselves).
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
