On Thu, Oct 31, 2013 at 11:26:27AM -0700, Anatol Pomozov wrote:
Hi
The sha1 is useful to people who need to quickly tell developers which version they are running when they're from git. Removing it is a bad idea.
You can get the commit from the version number even without the SHA1, something like:
git log --oneline $VERSION..$BRANCH | tail -n $REVISION | head -n 1
Where $BRANCH is the one used in PKGBUILD (usually it is HEAD).
This is not always true. Because of the branched, non-linear nature of git, you could have two 'version' that are the same with different SAH1s. The SHA is important in the version.
Anyway VCS-package users suppose to follow HEAD version closely. In those rare cases when a user sees problem in no-release non-HEAD version and tries to contact upstream developers I bet the first question from the developers will be "Could you please update to HEAD and see if the problem still exists?".
Yes, they will, but for bisecting where the problem is, you could really be happy for a SHA. Thanks, -- William Giokas | KaiSforza | http://kaictl.net/ GnuPG Key: 0x73CD09CF Fingerprint: F73F 50EF BBE2 9846 8306 E6B8 6902 06D8 73CD 09CF