Message: previous - next
Month: December 2011

Packaging naming with GIT

From: Darrell Anderson <humanreadable@...>
Date: Sat, 24 Dec 2011 08:48:32 -0800 (PST)
With SVN I used a package naming scheme based upon the previous official release number and SVN version:


With the official tarballs the package name excluded the SVN version:


I expect to continue that naming scheme with official release tarballs, although the version numbers change:


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?


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?