all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Greg Hogan <code@greghogan.com>, 60042@debbugs.gnu.org
Subject: [bug#60042] What to call pinned package versions
Date: Mon, 09 Jan 2023 11:32:20 +0100	[thread overview]
Message-ID: <87h6x0yp57.fsf@gmail.com> (raw)
In-Reply-To: <878rifxogc.fsf_-_@gnu.org>

Hi,

On ven., 06 janv. 2023 at 23:55, Ludovic Courtès <ludo@gnu.org> wrote:

>> Here, the suffix /fixed is confusing because it is used for the both
>> cases:
>>
>>  1) You use fixed to describe something which stays the same and does not
>>     or cannot vary.
>>  2) If you fix a problem or a bad situation, you deal with it and make it
>>     satisfactory.
>
> I know, English…  :-)
>
> The first instance of this pattern was ‘guile/fixed’, probably 10 years
> ago, so I guess it takes precedence.
>
> But maybe we could agree on ‘/pinned’ instead and adjust code
> accordingly?

Sorry, I miss your suggestion. :-)

From my understanding:

 + Option a.

version-control.scm:673:(define-public git-minimal/fixed -> git-minimal/pinned
linux.scm:7674:         (define-public libnftnl/fixed    -> libnftnl/pinned
samba.scm:295:          (define-public samba/fixed       -> samba/pinned
guile.scm:424:          (define-public guile-3.0/fixed   -> guile-3.0/pinned

 + Option b.

onc-rpc.scm:91:         (define libtirpc/fixed          -> libtirpc/grafted
gnupg.scm:257:          (define libksba/fixed           -> libksba/grafted
gnupg.scm:369:          (define gnupg/fixed             -> gnupg/grafted
linux.scm:2164:         (define-public util-linux/fixed -> util-linux/grafted
tls.scm:601:            (define openssl/fixed           -> openssl/grafted
xml.scm:159:            (define expat/fixed             -> expat/grafted
compression.scm:1890:   (define unzip/fixed             -> unzip/grafted

 + Option c. = option a. + option b. (remove reference to /fixed)


From my point of view, option a. is the less “disruptive” because for
instance we use the term “Fixes“ in commit message when a bug is indeed
fixed.

WDYT?

Cheers,
simon




  reply	other threads:[~2023-01-09 12:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 18:40 [bug#60042] [PATCH] gnu: git: Update to 2.39.0 Greg Hogan
2022-12-15 11:35 ` zimoun
2022-12-15 18:55   ` bug#60042: " Greg Hogan
2022-12-20 14:52   ` [bug#60042] " Ludovic Courtès
2022-12-20 15:38     ` Simon Tournier
2022-12-23 23:51       ` [bug#60042] Julia dependency on Git Ludovic Courtès
2022-12-30 13:15         ` zimoun
2023-01-03 17:59           ` Leo Famulari
2023-01-06 22:55           ` [bug#60042] What to call pinned package versions Ludovic Courtès
2023-01-09 10:32             ` Simon Tournier [this message]
2023-01-11 13:19               ` Simon Tournier
2023-01-11 17:27                 ` Ludovic Courtès
2023-01-11 17:26               ` Ludovic Courtès
2023-01-26 16:45                 ` zimoun
2022-12-20 16:38     ` [bug#60042] [PATCH] gnu: git: Update to 2.39.0 Greg Hogan
2022-12-25 16:18       ` Ludovic Courtès
2023-02-17 15:55         ` [bug#60042] open branches with target merge dates (was Re: [bug#60042] [PATCH] gnu: git: Update to 2.39.0.) Simon Tournier
2023-02-20 11:02           ` 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=87h6x0yp57.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=60042@debbugs.gnu.org \
    --cc=code@greghogan.com \
    --cc=ludo@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.