Well, I'm afraid these were all done by me, and at least for the emacs21
ones I'm in a bit of a quandry. The version number really can't change,
because the compile process needs to accurately know what it is.
The revision number contains that date of the CVS snapshot, but there
needs to be some wiggle-room to allow for move than one revision based
on a particular snapshot.
I was under the impression that version changes when the upstream data changes, and revision changes when the packaging changes. Is this correct?
If it is, then the date part of the revision in emacs21 really belongs in the version. So that yields
Version: 21.3.50cvs-20031224 Revision: 1
The only place Fink's version really matters to the build system is where %v is used--how else is the build system going to notice the version? So you can safely use any weird version you want, provided you replace the %v's with the `real` value, at the cost of making the package harder to update. If you're using a lot of %v's, you can make things a bit easier with something like this:
CompileScript: <<
#/bin/sh
export VERSION=`echo %v | sed -e 's/cvs.*//'`
do_something_with $VERSION
...
<<(If I'm wrong about the meanings of version and revision, then just do Revision: 20031224.12 instead of using a hyphen. Or use a + to delimit things. Or some digits.)
Dave
PGP.sig
Description: This is a digitally signed message part
