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?

kdebase-20120101_2200-i486-1.txz

More generally, should we adopt a common package naming scheme, as much as possible within the limitations of each distro's package naming conventions? Might be nice if all of us use a somewhat similar naming scheme.

Ideas? Comments?

Darrell