From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: bug-guix@gnu.org
Subject: Re: Problem with texinfo 5.0 package
Date: Wed, 20 Feb 2013 23:45:52 +0100 [thread overview]
Message-ID: <87hal6li3j.fsf@gnu.org> (raw)
In-Reply-To: <87mwuyfygu.fsf@tines.lan> (Mark H. Weaver's message of "Wed, 20 Feb 2013 16:48:49 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> The built texinfo 5.0 packages contain a few uses of 'perl' that are not
>>> pointing to a specific version in /nix/store:
>>
>> Yes, I know, but since in ‘core-updates’ we’ll change ‘patch-shebang’ to
>> handle /usr/bin/env specially, that’ll work well there.
>
> Unless I'm mistaken, that will fix only 2 out of 4 of the occurrences:
>
> ./bin/pod2texi:1:#!/nix/store/777jas1fcgc38hmvq6lq1sa9k67f10kl-coreutils-8.20/bin/env perl
> ./bin/texi2dvi:1437: perl -pe 's<\\documentclass(?:\[.*\])?{.*}>
> ./bin/texi2dvi:1544: perl -pi -e 's/[ \t]+$//g' "$out_base"*;;
> ./bin/texi2any:1:#!/nix/store/777jas1fcgc38hmvq6lq1sa9k67f10kl-coreutils-8.20/bin/env perl
Indeed, sorry for overlooking that.
That’s a case for ‘wrap-program’, also scheduled for ‘core-updates’.
(Note that f6d7be1 fixes all of them, because it puts Perl in $PATH, but
that’s obviously not the best solution.)
Thanks,
Ludo’.
prev parent reply other threads:[~2013-02-20 22:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 5:00 Problem with texinfo 5.0 package Mark H Weaver
2013-02-20 11:29 ` Ludovic Courtès
2013-02-20 18:42 ` Mark H Weaver
2013-02-20 19:49 ` carl hansen
2013-02-20 20:58 ` Ludovic Courtès
2013-02-20 21:45 ` Mark H Weaver
2013-02-20 20:09 ` Ludovic Courtès
2013-02-20 21:48 ` Mark H Weaver
2013-02-20 22:45 ` Ludovic Courtès [this message]
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=87hal6li3j.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=mhw@netris.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).