GNU bug report logs - #74542
[PATCH 00/11] Improved tooling for package updates

Previous Next

Package: guix-patches;

Reported by: Ludovic Courtès <ludo <at> gnu.org>

Date: Tue, 26 Nov 2024 10:33:01 UTC

Severity: normal

Tags: patch

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #188 received at 74542 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: Josselin Poiret <dev <at> jpoiret.xyz>,
 Simon Tournier <zimon.toutoune <at> gmail.com>, Mathieu Othacehe <othacehe <at> gnu.org>,
 Tobias Geerinckx-Rice <me <at> tobias.gr>, 74542 <at> debbugs.gnu.org,
 Christopher Baines <guix <at> cbaines.net>
Subject: Re: [bug#74542] [PATCH v2 05/16] packages: Factorize
 ‘all-packages’.
Date: Sun, 01 Dec 2024 17:37:05 +0100
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:

>> @@ -253,6 +254,23 @@ (define* (fold-packages proc init
>>                                  init
>>                                  modules))
>>  
>> +(define all-packages
>> +  (mlambda ()
>> +    "Return the list of all public packages, including replacements and hidden
>> +packages, excluding superseded packages."
>
> Reading the above doc made me question; are replacements always supposed
> to be made public?  I typically would leave them private to avoid
> cluttering the CLI with duplicate packages.

Replacements are always reachable via the ‘replacement’ field, whether
they’re public or not.

If they’re public, they’re also visible from the user interface, which
is probably nicer.  Other than that, it doesn’t make a big difference.

Ludo’.




This bug report was last modified 169 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.