all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: guix-devel@gnu.org
Subject: Texlive and native-inputs
Date: Wed, 29 Oct 2014 18:00:02 +0100	[thread overview]
Message-ID: <20141029165958.GA4944@debian.eduroam.u-bordeaux.fr> (raw)

Currently, texlive has a certain number of native inputs:
   (native-inputs
    `(("perl" ,perl)
      ("pkg-config" ,pkg-config)
      ("python" ,python-2) ; incompatible with Python 3 (print syntax)
      ("tcsh" ,tcsh)))
But I think these are not needed during build time, but to patch-shebang
scripts that are installed into the bin directory. So should they not be
normal inputs?

This is part of commit c4c4cc05979f2a2d0212963c5fe1b940d63a0958 which was
a mass-move from inputs to native-inputs. I wonder if these need to be
verified one by one by hand? How does one know without going through every
line of the build logs whether an interpreter is used during the build
or in installed scripts? Or what happens if both is the case?

Did I misunderstand anything?

Andreas

             reply	other threads:[~2014-10-29 17:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 17:00 Andreas Enge [this message]
2014-10-29 17:13 ` Texlive and native-inputs 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
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=20141029165958.GA4944@debian.eduroam.u-bordeaux.fr \
    --to=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.