From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: Better names for Guix versions from git? Date: Wed, 26 Dec 2018 15:02:22 +0100 Message-ID: <87k1jw8jyp.fsf@fastmail.com> References: <87lg4dwfmt.fsf@gmail.com> <351d14fe-0edd-6575-939d-981598b65255@riseup.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36264) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gc9lW-0003FX-40 for guix-devel@gnu.org; Wed, 26 Dec 2018 09:02:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gc9lS-000614-V8 for guix-devel@gnu.org; Wed, 26 Dec 2018 09:02:30 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:50501) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gc9lS-00060H-RR for guix-devel@gnu.org; Wed, 26 Dec 2018 09:02:26 -0500 In-Reply-To: <351d14fe-0edd-6575-939d-981598b65255@riseup.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: swedebugia , guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable swedebugia writes: > On 2018-12-25 20:49, Taylan Kammer wrote: >> Currently, after running 'guix pull', the Guix version will be reported >> by 'guix --version' as something like: >>=20 >> 522d1b87bc88dd459ade51b1ee0545937da8d3b5 >>=20 >> I think it would be really nice if instead it were something like: >>=20 >> 2018-12-25-522d1b >>=20 >> where the date is the commit's date (year, month, day) in UTC+0. >>=20 >> That's shorter, more descriptive, and just as unique. (The chances of >> there being two commits in the same day with the same first 6 positions >> in the hash should be negligient.) >>=20 >> The package name is currently something like: >>=20 >> guix-522d1b87b >>=20 >> That could become: >>=20 >> guix-2018-12-25-522d1b >>=20 >> which is a bit longer but more descriptive. >>=20 >> I looked into guix/self.scm a bit but couldn't easily tell how difficult >> it would be to implement these changes. >>=20 >> Thoughts? Worth it? > > I think it is worth it, in fact I was on my way to suggest the same. I like the "git describe" format: $ git describe v0.16.0-414-ge99d036828 It does not mention a date, but it can be copy-pasted into "git" and shows how many commits there were between each generation. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlwjie4ACgkQoqBt8qM6 VPqppggAkQr3CWeunHGuceVlD0pcEY8derRW4ZTF6Bi6aodQqm+5cllC13vDPWwp pJfYR/zkbFEeiXsz/AxhJpAQLH/Z7LBhfr5Bxc4Htzbl6rTYgM7/BqsYsSPu8L7W AIH1nn7HhtdReuBpdndc73M/Bm6fJRzEW0nJib7WLvsiyO3aIgbfprZv2o7elkfd zUBU8AD7xp5NUzy+f7Bq2YCGW+bs7bq9ykX9nZFIyoHP48IB6NysAirN9y/UMdLj 1skCZ430eseTXNAmls0uY/UUVUA2TLOlXrA6gopGTpOaGzQyM3GzVlw9wDC1Yp5I TBwLCjW/C8CLRt7bocNA2kVkDPVD/Q== =232W -----END PGP SIGNATURE----- --=-=-=--