Hi Simon.
For English speakers, I didn't understood that before gc I
must forget
the roots. That is why the space wasn't liberated.
I can't pretend to understand fully - but new user eyes on a
piece of
software is always something to pay attention to - and I may
guess wrong
what the mis-conception was here, but I found the
mis-conception I'm
thinking of interesting, so bear with me.
Just to clarify what happened with me -before going into
solutions-: I
read the manual regarding cg and didn't understood that roots
must be
liberated or forgotten before in order to be collected (see
https://guix.gnu.org/manual/en/html_node/Invoking-guix-gc.html).
That node explicitly says:
Packages that are installed, but not used, may be
garbage-collected.
The guix gc command allows users to explicitly run the
garbage
collector to reclaim space from the /gnu/store directory.
And then only mentions roots:
The garbage collector has a set of known roots: any file
under
/gnu/store reachable from a root is considered live and
cannot be
deleted; any other file is considered dead and may be
deleted.
So, even reading the manual it was not clear (to me at least)
that I
must liberate or forget roots before running gc.
It seems there could be a mode (perhaps by default) where
'guix
upgrade' would do 1) upgrade to a new generation, and then 2)
[...] I
don't expect my idea to actually be implemented, but maybe it
humours
someone to think about this from a new user perspective. [...]
From a UX researcher and designer point of view, we must:
1. understand the current situation as integrally as possible
(actors,
context, tasks, etc.).
2. Define the desired outcome.
3. Design the solution.
Being new I wouldn't even dream about debating on what is a sane
or
desired default. I'm only saying that we must agree on the
desired
outcome first, and your reflections help us to do exactly that,
so thank
you. :)
--
eduardo mercovich
Donde se cruzan tus talentos
con las necesidades del mundo,
ahí está tu vocación.
(Anónimo)
