# from David Golden
# on Wednesday 20 August 2008 11:27:
>> The reason, for me, is that generating META.yml is almost always
>> predictable
>
>My view:
>
>* META.yml is an evolving spec
>* The build tools are periodically updated to produce the latest
> current spec
> * Storing META.yml in the repository has almost zero marginal cost[1]
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.)
My build/tag/ship tool also requires that everything is fully committed
before the build, with no changes to versioned files during the build,
so the distmeta point where META.yml changes is just annoying.
--Eric
--
We who cut mere stones must always be envisioning cathedrals.
--Quarry worker's creed
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
