# from David Golden
# on Wednesday 20 August 2008 14:57:
>>>For me, the tag *is* the release.
>
>I meant that metaphorically.
Yeah, but how metaphorically? If a recursive diff on (e.g.) 'svn export
$tag' and the unpacked tarball produces output, then the tag == the
release.
>No, my repository can contain files that may not be released (though
>it usually doesn't). But everything released can be found in the
>repository. The release is still created using "Build dist" -- but
>the tools make sure MANIFEST and meta files are updated beforehand.
So, your tag is a superset of the release. For me, the tag is the tree
I had when I built the release. If I need to exactly replicate the
meta content of the tarball, that might not be possible if the
generator tools have changed, but that's not a problem in the code and
if anything it is a reason to ship a new release (and thus create a new
tag (at which point anything wrong with the old meta stuff doesn't
matter)), so the tag serves as a checkpoint of the code functionality
and the rest can be found elsewhere if it even matters.
(And if you can't find the tarball on the backpan, it doesn't exist!)
--Eric
--
[...proprietary software is better than gpl because...] "There is value
in having somebody you can write checks to, and they fix bugs."
--Mike McNamara (president of a commercial software company)
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
