With SVN I used a package naming scheme based upon the previous official release number and SVN version:
kdebase-3.5.12-125202-i486-1.txz
With the official tarballs the package name excluded the SVN version:
kdebase-3.5.13-i486-1.txz
I expect to continue that naming scheme with official release tarballs, although the version numbers change:
kdebase-r14.0-i486-1.txz
Enter GIT.
GIT uses a weird hash number for each patch version. Is there a more straightforward version number? Or will I have to start naming GIT builds using a date and time scheme?
<snip>
The Debian/Ubuntu builds utilize the revision *count*, that is, the number of commits that have been made to each module.
You can get this number by using the following (nasty, complex, and completely unobvious) command: git shortlog . | grep -E '^[ ]+\w+' | wc -l
SVN was much easier in this regard. ;-)
Tim
Also I should mention that it is a good idea to include the full GIT hash in a changelog somewhere, because there is no way to easily go from the revision count to the GIT hash as listed on the TDE patches page.
Tim