unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: texlive-20190410-texmf.tar.xz again and again
Date: Fri, 10 Jul 2020 13:04:24 +0200	[thread overview]
Message-ID: <87lfjrzl53.fsf@nckx> (raw)
In-Reply-To: <86h7ufbqq9.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]

Simon,

zimoun 写道:
> I am often annoyed because when I run "guix upgrade", Guix
> downloads again the heavy texlive-20190410-texmf.tar.xz if I 
> have
> forgotten to protect it from "guix gc" using the trick, e.g.,
>
>   https://lists.gnu.org/archive/html/help-guix/2020-02/msg00110.html
>
> What could be a more general solution independent of the trick?

You might be happy with ‘--gc-keep-outputs’.

From (guix)Invoking guix-daemon:

‘--gc-keep-outputs[=yes|no]’
     Tell whether the garbage collector (GC) must keep outputs of 
     live
     derivations.

     When set to ‘yes’, the GC will keep the outputs of any live
     derivation available in the store—the ‘.drv’ files.  The 
     default is
     ‘no’, meaning that derivation outputs are kept only if they 
     are
     reachable from a GC root.  *Note Invoking guix gc::, for more 
     on GC
     roots.

‘--gc-keep-derivations[=yes|no]’
     Tell whether the garbage collector (GC) must keep derivations
     corresponding to live outputs.

     When set to ‘yes’, as is the case by default, the GC keeps
     derivations—i.e., ‘.drv’ files—as long as at least one of 
     their
     outputs is live.  This allows users to keep track of the 
     origins of
     items in their store.  Setting it to ‘no’ saves a bit of disk
     space.

     In this way, setting ‘--gc-keep-derivations’ to ‘yes’ causes
     liveness to flow from outputs to derivations, and setting
     ‘--gc-keep-outputs’ to ‘yes’ causes liveness to flow from
   ▶ derivations to outputs.  When both are set to ‘yes’, the 
   effect is
   ▶ to keep all the build prerequisites (the sources, compiler,
   ▶ libraries, and other build-time tools) of live objects in the
     store, regardless of whether these prerequisites are 
     reachable from
     a GC root.  This is convenient for developers since it saves
     rebuilds or downloads.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2020-07-10 11:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 10:37 texlive-20190410-texmf.tar.xz again and again zimoun
2020-07-10 11:04 ` Tobias Geerinckx-Rice [this message]
2020-07-10 14:15   ` zimoun
2020-07-10 12:11 ` Ricardo Wurmus
2020-07-10 14:11   ` zimoun

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=87lfjrzl53.fsf@nckx \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).