On Wed, Aug 20, 2008 at 2:55 PM, Eric Wilhelm <[EMAIL PROTECTED]> wrote: > Umm, is that for or against storing META.yml in the repo? For me, the > cost of checking it in is that you continually have to confront the > regen/diff/commit issues for a file where the differences don't really > mean anything (and thus I get no value from the effort of tracking > them.)
Now that META.yml has the potential to have a configure-time effect by way of the "configure_requires" field, I view the META.yml to be part of the source -- albeit a generated one -- and therefore, I want it checked in, particularly since the META.yml in a release is dependent on the particular EU::MM or M::B I had installed on whatever machine I happened to be working on at the time I released the code. I don't archive my tarballs, and while I suppose I could always get really old ones off BackPAN, I'd rather just have it all in my repository so I can just checkout tag X.YY and have it if I should need it. Since this is part of the same religious war, I'll leave it at that. This is how I do it, and people are welcome to make their own choices. David
