Re: Texlive and native-inputs

[John Darrington <john@darrington.wattle.id.au>]

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

On Wed, Oct 29, 2014 at 07:51:44PM +0100, Andreas Enge wrote:
     On Wed, Oct 29, 2014 at 06:39:48PM +0100, Andreas Enge wrote:
     > Would it work? One would need to patch-shebang with the normal input and
     > use the native-input for scripts that are used during the build process.
     > Is this distinguished somehow? (Well, there is of course the problem of
     > scripts that are used during the build process _and_ installed on the user's
     > machine, which means that the package is simply not cross-compilable in
     > our setting.
     
     In a sense this is what happens with texlive. "make check" uses perl scripts,
     and other perl scripts are installed.
     
     But then I suppose that "make check" does not make much sense anyway when
     cross-compiling? Do we activate it then?

Supposing it was possible to run "make check" on a cross-compiled build (for 
example using an emulator), then we would need the non-native perl.
The installed perl scripts also need the non-native perl.  

So it looks as if the the native perl is not needed at all.   


What do these scripts do anyway?  Are they fundamental to TeXlive or are they for some bells and whistles?

J'

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