<thomasd>what would be a good way to prevent the (patched) texlive-...-texmf source from being gc'ed?
<roelj>thomasd: I think by making sure it has a link in <state-dir>/gcroots. So if you'd install it in a profile, that'd do it.
<thomasd>I find myself downloading and patching that thing every time I upgrade my packages, but I think I could actually keep the patched texmf tarball and save a lot of time (bandwidth)
<roelj>thomasd: Oh.. source tarball.. You could also keep a local copy and patch the recipe to use the file:///path/to/tarball.tar.gz instead.
<thomasd>roelj: I don't know how to install it, because it's not a package (it's defined but not exported in tex.scm), is there a way to force that? is it ok to manually put a symlink in /var/guix/gcroots
<thomasd>roelj: yes, that's my plan B :) But I think I'm not the only one facing this problem (the proper solution is the ongoing (?) heroic attempt at modularizing the texlive packages, I suppose)
<ng0>cbaines: ah! nice. I forgot about "/../" giving you the level above "."
<roelj>thomasd: I think manually putting a link in /var/guix/gcroots will work, as long as the tarball does not change.
<roelj>How would I load a manifest file into a Scheme symbol?