[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Texlive and native-inputs
From: |
Andreas Enge |
Subject: |
Texlive and native-inputs |
Date: |
Wed, 29 Oct 2014 18:00:02 +0100 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
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
- Texlive and native-inputs,
Andreas Enge <=
- Re: Texlive and native-inputs, John Darrington, 2014/10/29
- Re: Texlive and native-inputs, Andreas Enge, 2014/10/29
- Re: Texlive and native-inputs, John Darrington, 2014/10/29
- Re: Texlive and native-inputs, Andreas Enge, 2014/10/29
- Re: Texlive and native-inputs, John Darrington, 2014/10/29
- Re: Texlive and native-inputs, Andreas Enge, 2014/10/29
- Re: Texlive and native-inputs, John Darrington, 2014/10/30
- Re: Texlive and native-inputs, Andreas Enge, 2014/10/30
- Re: Texlive and native-inputs, John Darrington, 2014/10/30
- Re: Texlive and native-inputs, Ludovic Courtès, 2014/10/29