From: "Ludovic Courtès" <ludo@gnu.org>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: "Christopher Baines via Development of GNU Guix and the GNU
System distribution." <guix-devel@gnu.org>,
Sarah Morgensen <iskarian@mgsn.dev>
Subject: Re: Can we find a better idiom for unversioned packages?
Date: Wed, 08 Sep 2021 23:15:34 +0200 [thread overview]
Message-ID: <87h7euzs3t.fsf@gnu.org> (raw)
In-Reply-To: <87fsuojl43.fsf@yoctocell.xyz> (Xinglu Chen's message of "Wed, 01 Sep 2021 18:50:36 +0200")
Hi,
Xinglu Chen <public@yoctocell.xyz> skribis:
> Well, seeing
>
> foo-1.0.0-1.2021-01-31
>
> gives a user more useful information than something like
>
> foo-1.0.0-1.cabba9e
>
> With the former, I can quickly see that the version is from 2021-01-31,
> whereas with the latter, I would have to either find the VCS repo online
> or go to my local checkout of it and browse the logs.
I agree with Leo here. IMO what matters with version strings is that
they be comparable: users (and UIs) should be able to tell which string
denotes a newer version. That’s exactly what the ‘revision’ bit does in
the example above. The commit shorthand is an additional bit to
uniquely identify the snapshot.
Knowing the date of a release, or that of a commit, may also be useful,
but that’s not what version strings are about generally.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-09-08 21:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 19:57 Can we find a better idiom for unversioned packages? Sarah Morgensen
2021-08-31 21:20 ` Maxime Devos
2021-09-01 12:11 ` Xinglu Chen
2021-09-01 16:29 ` Maxime Devos
2021-09-01 13:33 ` Liliana Marie Prikler
2021-09-01 16:39 ` Maxime Devos
2021-09-01 18:34 ` Liliana Marie Prikler
2021-09-02 14:09 ` Maxime Devos
2021-09-02 14:20 ` Liliana Marie Prikler
2021-09-02 14:34 ` Maxime Devos
2021-09-01 19:48 ` Jonathan McHugh
2021-09-01 21:47 ` Liliana Marie Prikler
2021-09-02 13:32 ` Maxime Devos
2021-09-02 7:53 ` Jonathan McHugh
2021-09-02 9:25 ` Liliana Marie Prikler
2021-09-01 10:55 ` Xinglu Chen
2021-09-01 15:37 ` Leo Famulari
2021-09-01 16:50 ` Xinglu Chen
2021-09-02 16:51 ` Leo Famulari
2021-09-02 17:29 ` Leo Famulari
2021-09-03 16:11 ` Xinglu Chen
2021-09-03 16:35 ` Leo Famulari
2021-09-03 16:57 ` Leo Famulari
2021-09-03 20:03 ` Xinglu Chen
2021-09-04 21:00 ` Leo Famulari
2021-09-08 21:15 ` Ludovic Courtès [this message]
2021-09-02 17:08 ` Leo Famulari
2021-09-08 21:28 ` Ludovic Courtès
2021-09-08 22:21 ` Jonathan McHugh
2021-09-08 22:38 ` Leo Famulari
-- strict thread matches above, loose matches on Subject: below --
2021-09-03 5:51 Sarah Morgensen
2021-09-03 21:14 Sarah Morgensen
2021-09-03 22:11 ` Liliana Marie Prikler
2021-09-04 12:32 ` Taylan Kammer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7euzs3t.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=iskarian@mgsn.dev \
--cc=public@yoctocell.xyz \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).