unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: More robust substitute*
Date: Sun, 03 Feb 2013 18:56:26 +0100	[thread overview]
Message-ID: <87ip6946yd.fsf@gnu.org> (raw)
In-Reply-To: <201302021822.02436.andreas@enge.fr> (Andreas Enge's message of "Sat, 2 Feb 2013 18:22:02 +0100")

Hello!

Andreas Enge <andreas@enge.fr> skribis:

> 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.

Ah right, the ‘patch-shebangs’ phase just looks at files in ‘bin’ and
‘sbin’ (see gnu-build-system.scm).

Perhaps you can add a phase somewhere that does along the lines of:

  (lambda* (#:key outputs #:allow-other-keys)
    (for-each (match-lambda
                ((_ . dir)
                 (for-each patch-shebang
                           (find-files (string-append dir "/share")
                                       ".*"))))
              outputs)
    #t)

> 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!

Woow, congratulations!  :-)

I’m not sure if that would help here, but do you know about
“multiple-output derivations”?  It’s used for Libtool for instance: the
‘outputs’ field there means that binaries go into one directory, and the
rest goes into another directory (you see them when typing ‘guix-build
libtool’).

So if there are several kinds of files, you may want to separate them in
different outputs.

> 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.

Hmm, intriguing.  :-)

Thanks!

Ludo’, coming back from FOSDEM.

  reply	other threads:[~2013-02-03 17:56 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
2013-02-03 17:56     ` Ludovic Courtès [this message]
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=87ip6946yd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=bug-guix@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).