[XeTeX] Patches for XeTeX installation scripts (XeTeX on FreeBSD + more)

Jonathan Kew jonathan_kew at sil.org
Wed Jul 11 21:33:31 CEST 2007


On 11 Jul 2007, at 4:37 am, Nikola Lecic wrote:

> I understand; at the end of ends, TL installation scripts install
> pre-compiled binaries to a random directory and they work, but it
> probably depends on other parts of TL config...

As far as I know, the crucial part is that the binary finds  
texmf.cnf; everything else is derived from that. texmf.cnf is usually  
found (in TeX Live) in a location relative to the binary (using the  
kpse $SELFAUTOPARENT variable or something like that), but there is a  
compiled-in path that would be used if other forms of search failed.  
And therefore redistributors may want to set that path to one that  
makes sense for their distro.


>
> That's it, I've successfully compiled rev. 503. Just one tiny thing;
> sed argument must have double quotes here:
>
>   WEB2CDIR=`echo ${WEB2CDIR} | sed -e 's!${REALPATHPREFIX}!$ 
> {PREFIX}!'`
>
> (this way the variables inside s/// are not simultaneously  
> expanded) --
> two occurences in runConfigure.sh and one in build-xetex.

I think there are two such sed commands each in runConfigure.sh and  
build-xetex, actually.

Sorry, but could you clarify exactly where you'd like quotes added to  
this? An extra level of quotes around the sed argument as a whole, or  
change from single to double quotes, or what? I'm not sufficiently  
sure of the shell quoting rules, etc....


>
> Now, if there is no plan for replacing these scripts with standard
> 'configure/make/make install' in the near future -- and if you  
> agree --
> I'd gladly try to do it. Is there anything special that should be  
> taken
> into consideration in understanding this task (something related to TL
> building, for example -- than can make it too complex)?

The main consideration, in my mind, would be to try and keep the  
configure/make pieces in the "standalone" xetex repository and those  
in the TL repository as close to identical as possible. I don't want  
to have two different build setups that need to be maintained; I'd  
like to be able to synchronize changes to the xetex-related parts of  
configure.in files, etc., as well as the xetex.mk makefile fragment,  
between the xetex and TL repositories.

So this means that if you want to streamline the xetex build scripts  
-- which I agree would be a good thing -- please try to ensure that  
the resulting files still work correctly within the context of a full  
TeX Live build.

JK




More information about the XeTeX mailing list