From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: More robust substitute*
Date: Sat, 2 Feb 2013 18:22:02 +0100 [thread overview]
Message-ID: <201302021822.02436.andreas@enge.fr> (raw)
In-Reply-To: <878v767kho.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
Am Samstag, 2. Februar 2013 schrieb Ludovic Courtès:
> Andreas Enge <andreas@enge.fr> skribis:
> > in texlive, there are lots of scripts to be installed in share; thus,
> > the patch-shebang phase does not catch them.
> Do you know why it doesn’t catch them? The ‘patch-source-shebangs’
> phase patches all the files found under “.”, recursively.
I am not speaking about patch-source-shebangs, but patch-shebangs. Texlive
consists of three source packages. The first one contains the source for
the binaries, the other two contain files to be installed under "share". I
unpack these after the installation procedure and copy them to "share".
But if patch-source-shebangs works recursively, I should maybe unpack
everything first and let it do its magic. I will give it a try.
In any case, I have a working texlive! It contains over 100000 files (that
are symlinked from the user profile...) and takes over 3GB, but it works!
Actually, I think one does not need to symlink the files from the user
profile; tex has its own way of finding files via the binary "kpsewhich"
(linked from the user profile), which points directly to the nix store:
$ kpsewhich article.sty
/nix/store/2cc4xyivn5f52gywl5mnz6fi90bj24xh-texlive-2012/share/texmf-
dist/tex/latex/base/article.sty
So maybe by splitting into two or three packages, one could hide the data
in the nix store. I will think about it.
Andreas
[-- Attachment #2: Type: text/html, Size: 4876 bytes --]
next prev parent reply other threads:[~2013-02-02 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 16:14 More robust substitute* Andreas Enge
2013-02-02 16:23 ` Ludovic Courtès
2013-02-02 17:22 ` Andreas Enge [this message]
2013-02-03 17:56 ` Ludovic Courtès
2013-02-03 18:03 ` 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
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=201302021822.02436.andreas@enge.fr \
--to=andreas@enge.fr \
--cc=bug-guix@gnu.org \
--cc=ludo@gnu.org \
/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).