On Tue, April 21, 2009 6:16 pm, Adam Kennedy wrote: > 2009/4/22 Yitzchak Scott-Thoennes <sthoe...@efn.org>: > >> I didn't see any "in META.yml" restriction in David's dicta. And I >> would be very surprised if META.yml publicized a different version than I >> picked. > > META.yml is a machine to machine format, theoretically humans aren't > even supposed to be reading it except for debugging purposes.
Sorry, I worded that sloppily. I meant "META.yml publicized and tools reading it displayed to humans a different version". It comes down to: why is the version in META.yml? That is, how will tools reading it use it? That should determine what is stored in META.yml. > It's quite acceptable for the value in META.yml to be a normalised > different string to what is in the module. Off the top of my head, the two possible purposes are 1) comparison with another version and 2) display. For 1), I can see wanting to have a normalized version so that non-perl tools (tools that can't easily use version.pm to normalize) can behave sensibly. For 2) a normalized version is unacceptable, in my view. But I'm just guessing at the reason for suggesting a normalized version be stored (or, as I possibly misunderstood it earlier, that only already normalized versions be used anywhere). I'd like to hear a succinct account of the reasons people may have.
