[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#33285: Installing, then removing, a package yields a different profi
From: |
Ludovic Courtès |
Subject: |
bug#33285: Installing, then removing, a package yields a different profile |
Date: |
Wed, 06 Feb 2019 14:19:26 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Ludovic Courtès <address@hidden> 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.
Thoughts?
Ludo’.
- bug#33285: Installing, then removing, a package yields a different profile, Ricardo Wurmus, 2019/02/03
- bug#33285: Installing, then removing, a package yields a different profile, Ludovic Courtès, 2019/02/04
- bug#33285: Installing, then removing, a package yields a different profile,
Ludovic Courtès <=
- bug#33285: Installing, then removing, a package yields a different profile, Ricardo Wurmus, 2019/02/06
- bug#33285: Installing, then removing, a package yields a different profile, Jelle Licht, 2019/02/07
- bug#33285: Installing, then removing, a package yields a different profile, Chris Marusich, 2019/02/08