Mark H Weaver writes:
...
> On my GuixSD system where substitutes are completely disabled and I
> build everything locally, I've been running my Guix daemon with both
> --gc-keep-derivations=yes and --gc-keep-outputs=yes for years. Here's
> the relevant excerpt of my OS config:
>
>
Mark H Weaver writes:
> The bootstrap binaries currently consist of statically-linked
> executables for 'bash', 'tar', 'xz', and 'mkdir', which are included in
> the Guix source tree in the gnu/packages/bootstrap/ directory:
>
>
George Clemmer writes:
> Mark H Weaver writes:
>
>> On my GuixSD system where substitutes are completely disabled and I
>> build everything locally, I've been running my Guix daemon with both
>> --gc-keep-derivations=yes and --gc-keep-outputs=yes for years. Here's
>> the relevant excerpt of my
Hi Mark,
Mark H Weaver writes:
> On my GuixSD system where substitutes are completely disabled and I
> build everything locally, I've been running my Guix daemon with both
> --gc-keep-derivations=yes and --gc-keep-outputs=yes for years. Here's
> the relevant excerpt of my OS config:
...
Hi Joshua,
Joshua Branson writes:
> Mark H Weaver writes:
>
>> Pierre Neidhardt writes:
>>
>> On my GuixSD system where substitutes are completely disabled and I
>> build everything locally, I've been running my Guix daemon with both
>> --gc-keep-derivations=yes and --gc-keep-outputs=yes for
Hello,
Matthew Brooks skribis:
> Is there any recommended way to have guix gc only delete packages that aren't
> required to build anything?
To complement what others say, I use a low-tech but good enough
approach, which is to GC just as much as I need, e.g., by running
“guix gc -F80G” once
Mark H Weaver writes:
> Pierre Neidhardt writes:
>
> On my GuixSD system where substitutes are completely disabled and I
> build everything locally, I've been running my Guix daemon with both
> --gc-keep-derivations=yes and --gc-keep-outputs=yes for years. Here's
> the relevant excerpt of my
Pierre Neidhardt writes:
>> Contrary to what Pierre wrote above, I've found that the use of these
>> flags certainly does _not_ lead to an ever-growing store.
>
> According to the discussion I linked above, The reason behind the ever-growing
> store are substitutes. So if you don't use them,
> Contrary to what Pierre wrote above, I've found that the use of these
> flags certainly does _not_ lead to an ever-growing store.
According to the discussion I linked above, The reason behind the ever-growing
store are substitutes. So if you don't use them, then the store size should be
Pierre Neidhardt writes:
> I've been bugged by this as well (see
> https://lists.gnu.org/archive/html/help-guix/2018-09/msg00028.html). There
> are
> a few options beside Ricardo's suggestion:
>
> - You can start the Guix daemon with --gc-keep-outputs (see "(guix) Invoking
> guix-daemon" in
Hi Matthew,
> Is there any recommended way to have guix gc only delete packages that
> aren't required to build anything?
This requirement is a little vague. Do you mean to only delete leaf
packages? Or do you just want to keep a version of GCC?
You could create an environment containing
Is there any recommended way to have guix gc only delete packages that aren't
required to build anything?
I've made a custom bash script that loops through the output of "guix gc
--list-dead" and tells guix to delete any dead packages that have no
--referers, but it's really slow (it can take
12 matches
Mail list logo
