all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: guix-devel@gnu.org
Subject: Re: Better names for Guix versions from git?
Date: Tue, 25 Dec 2018 22:45:59 +0100	[thread overview]
Message-ID: <351d14fe-0edd-6575-939d-981598b65255@riseup.net> (raw)
In-Reply-To: <87lg4dwfmt.fsf@gmail.com>

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:
> 
>      522d1b87bc88dd459ade51b1ee0545937da8d3b5
> 
> I think it would be really nice if instead it were something like:
> 
>      2018-12-25-522d1b
> 
> where the date is the commit's date (year, month, day) in UTC+0.
> 
> 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.)
> 
> The package name is currently something like:
> 
>      guix-522d1b87b
> 
> That could become:
> 
>      guix-2018-12-25-522d1b
> 
> which is a bit longer but more descriptive.
> 
> I looked into guix/self.scm a bit but couldn't easily tell how difficult
> it would be to implement these changes.
> 
> Thoughts?  Worth it?

I think it is worth it, in fact I was on my way to suggest the same.

-- 
Cheers Swedebugia

  reply	other threads:[~2018-12-25 21:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-25 19:49 Better names for Guix versions from git? Taylan Kammer
2018-12-25 21:45 ` swedebugia [this message]
2018-12-26 13:57   ` Gábor Boskovits
2018-12-30  2:48     ` Vagrant Cascadian
2018-12-31 12:45       ` Hartmut Goebel
2018-12-26 14:02   ` Marius Bakke
2018-12-27 21:30     ` Taylan Kammer
2018-12-29 11:53       ` Björn Höfling
2018-12-29 16:39         ` swedebugia
2018-12-29 22:50           ` Ricardo Wurmus
2018-12-29 23:52             ` Björn Höfling
2019-01-05 17:45     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=351d14fe-0edd-6575-939d-981598b65255@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.