From: Thomas Danckaert <post@thomasdanckaert.be>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: prevent gc of texlive-...-texmf.tar.xz
Date: Thu, 13 Feb 2020 17:21:48 +0100 [thread overview]
Message-ID: <90fc7408793e133277a7e9cf4e412256@thomasdanckaert.be> (raw)
In-Reply-To: <20200212204505.GB17839@jasmine.lan>
On 2020-02-12 21:45, Leo Famulari wrote:
> The simplest way to make a gcroot is to symlink the store item into
> /var/guix/gcroots.
>
> In fact, I've had this exact symlink for a few years now:
>
> lrwxrwxrwx 1 root root 73 Aug 5 2017 texlive-20170524-texmf.tar.xz
> ->
> /gnu/store/5rnvmy02yazy8iwaa91kijbbqp8qmflz-texlive-20170524-texmf.tar.xz
Ah, thanks, that should do it! I wondered if I was the only one with
this problem.
@Zimoun: texlive-texmf.tar.xz is only a build input of texlive, so it
can be gc'ed even when texlive is installed in a profile. As far as I
remember, updates to texlive often seem to require the original texmf
tarball and apply patches to it (not sure how this works precisely --
somehow there are no substitutes for the patched/updated version of
texlive-texmf?). Interesting that you saw 2 downloads of texlive-texmf
(a 2.5GB nar file *and* the 2.5GB original tarball?). I don't
understand why that happens (but even in this case, eliminating at least
the tar.xz download saves a lot of time and bandwidth).
Thank you!
Thomas
next prev parent reply other threads:[~2020-02-13 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 12:53 prevent gc of texlive-...-texmf.tar.xz Thomas Danckaert
2020-02-12 18:08 ` zimoun
2020-02-12 20:45 ` Leo Famulari
2020-02-13 16:21 ` Thomas Danckaert [this message]
2020-02-23 17:19 ` Andreas Enge
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=90fc7408793e133277a7e9cf4e412256@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.