From: John Darrington <john@darrington.wattle.id.au>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Texlive and native-inputs
Date: Thu, 30 Oct 2014 10:24:13 +0100 [thread overview]
Message-ID: <20141030092413.GA2956@jocasta.intra> (raw)
In-Reply-To: <20141030080210.GA28331@debian>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
On Thu, Oct 30, 2014 at 09:02:10AM +0100, Andreas Enge wrote:
On Thu, Oct 30, 2014 at 08:53:24AM +0100, John Darrington wrote:
> In that case, it would seem to me, that perl should not be in input at all.
It should. Perl is needed for "make check". But even if it were not, we
always patch-shebang script files in our packages. Otherwise they would not
be usable, since we do not have /usr/bin/perl. That I personally do not
use these texlive scripts is not a reason to make them unusable!
It could be patched to "perl". That way, so long as the user has done
guix package -i perl it will work for him.
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-10-30 9:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 17:00 Texlive and native-inputs Andreas Enge
2014-10-29 17:13 ` John Darrington
2014-10-29 17:39 ` Andreas Enge
2014-10-29 17:52 ` John Darrington
2014-10-29 18:51 ` Andreas Enge
2014-10-29 19:55 ` John Darrington
2014-10-29 22:31 ` Andreas Enge
2014-10-30 7:53 ` John Darrington
2014-10-30 8:02 ` Andreas Enge
2014-10-30 9:24 ` John Darrington [this message]
2014-10-29 22:37 ` Ludovic Courtès
2014-10-29 22:29 ` Ludovic Courtès
2014-10-29 17:43 ` Andreas Enge
2014-10-29 18:03 ` John Darrington
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=20141030092413.GA2956@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=andreas@enge.fr \
--cc=guix-devel@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 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.