On Mon, Jun 01, 2015 at 02:18:01PM -0400, Greg Reagle wrote: > On Mon, Jun 1, 2015, at 01:46 PM, Jack L. Frost wrote: > > As a packager, I'd very much appreciate tagging once in a while so that > > we have > > static targets for patching and packaging. > > I don't know git well, just the basics, but why don't you use a git > commit id as the target for patching and packaging? As far as I > understand, a tag is just a "friendly" name for a commit id anyway.
If $APPLICATION versions 4541b821941a65e9c220acec2ab7256d7b21d690 and up support features X, Y and Z, can you tell me whether or not version 02e09b181db9b55d93a43a943d49048a4aeb0364 also has those features? This become even more of a nuisance when you only have immediate access to a compiled binary; I often build packages on one machine then distribute only the binaries. Using hashes for versioning means you can't $APPLICATION -V to easily figure out how old the binary is I'm using. Eric
