From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 33285@debbugs.gnu.org
Subject: bug#33285: Installing, then removing, a package yields a different profile
Date: Wed, 06 Feb 2019 15:29:16 +0100 [thread overview]
Message-ID: <871s4lgfcz.fsf@elephly.net> (raw)
In-Reply-To: <878sytawbl.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Ludovic Courtès <ludo@gnu.org> skribis:
>
>> Actually, to do things correctly, we should really store the .drv in the
>> ‘manifest’ file. That way, manifest entries would always contains a
>> valid “lowerable” object (a package or a derivation record), as opposed
>> to a store reference that happens to be valid.
>
> On second thought that’s probably not a great idea: we’d retain
> references to the .drv themselves, which can end up taking a bit of
> space, especially if --gc-keep-outputs is in use.
>
> So… the more I think about it the more I’m tempted to punt on this one.
>
> The discrepancy we see here does not happen when using --manifest, which
> is probably what matters most.
I think it’s fine to leave it as it is, then. “--install” and
“--remove” are stateful and should be expected to have quirks like this.
(E.g. upgrading Guix in between two “--install”s can lead to
a mosaic of a profile that could not be produced any other way.)
“--manifest” is the recommended way to get reproducible profile
generations, so if that’s working fine I’m okay with closing this as
wontfix. Chris, what do you think?
Thanks for investigating!
--
Ricardo
next prev parent reply other threads:[~2019-02-06 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 6:25 bug#33285: Installing, then removing, a package yields a different profile Chris Marusich
2018-11-06 14:25 ` Ludovic Courtès
2018-11-07 7:08 ` Chris Marusich
2019-02-03 23:14 ` Ricardo Wurmus
2019-02-04 18:02 ` Ludovic Courtès
2019-02-06 13:19 ` Ludovic Courtès
2019-02-06 14:29 ` Ricardo Wurmus [this message]
2019-02-07 11:11 ` Jelle Licht
2019-02-09 3:44 ` Chris Marusich
2019-03-12 11:58 ` Ricardo Wurmus
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=871s4lgfcz.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=33285@debbugs.gnu.org \
--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 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).