[OS X TeX] problems with Minion Pro package with gwTeX

[Bruno Voisin]

Le 31 mai 07 à 13:05, Peter Dyballa a écrit :

> Am 31.05.2007 um 10:15 schrieb Bruno Voisin:
>
>> Actually, if I'm not mistaken, upon install gwTeX makes updmap  
>> synonymous to updmap-sys.
>
> Bruno, you *are* mistaken here: both scripts are different! Updmap- 
> sys sets TEXMFVAR and TEXMFCONFIG to TEXMFSYSVAR resp.  
> TEXMFSYSCONFIG. Then updmap is called to do the real job on the  
> basis of these two variables set. The difference is that the output  
> of updmap-sys lands in a set of system-wide directories (/usr/local/ 
> gwTeX/texmf.local/fonts/map/*/updmap, /usr/local/texlive/2007/texmf- 
> var/fonts/map/*/updmap) while the "personal" updmap writes the MAP  
> files into the personal area at ~/Library/texmf/fonts/map/*/updmap.  
> Since both TEXMFSYSVAR and TEXMFSYSCONFIG are set to contain also  
> $HOMETEXMF, both updmap and updmap-sys read the MAP file fragments  
> form the system's area and from the user's private area. So it  
> makes a difference whether updmap-sys is invoked with a simple sudo  
> (then the proper user's HOMETEXMF area is searched) or with 'sudo - 
> H' 'sudo -H -u root' (then the root user's quite empty HOMETEXMF  
> area is searched).

Looking more closely at what the gwTeX i-Package does: you're right,  
updmap-sys and updmap aren't modified, it's only texmf.cnf that is  
affected.

Specifically, the tex.configure script inside the i-Package sets a  
parameter HomeTeXUse depending on the user's choice to request or not  
compatibility with pre-2004 TeXLive:

> if (not $simpleinstall) {
>     my $msg = "Do you want your TeX command line configuration to  
> be backwards compatible with pre-2004 versions? This is recommended  
> because most instructions for the use of TeX command line tools are  
> not only invalid for post-2004 TeX Live, but they also give  
> unexpected and unwanted results like administrator owned files in  
> your home directory.\n\nOnly if you know why you need your personal  
> settings (which this i-Package will ignore if you run it again in  
> the future), choose No.";
>     $doresult = `"${II2RESOURCES}/doalerter" -s "${II2DOSERVER}" -V  
> -t Alert -T "Do you want your CLI setup to be backwards  
> compatible?" -I \"${msg}\" -1 "Yes" -2 "No"`;
>     chomp( $doresult);
>     if ($doresult eq "Yes") {
> 	print "### ${PROGNAME}: Blocking personal configurations support  
> in ${II2INSTALLDIR}/texmf.cnf\n";
> 	setHomeTeXUse( 0);
>     }
>     else {
> 	print "### ${PROGNAME}: De-blocking personal configurations  
> support in ${II2INSTALLDIR}/texmf.cnf\n";
> 	setHomeTeXUse( 1);
>     }
> }
> else {
>     if ($previoustexmfcnf ne '') {
> 	if (ipkgsystem( "egrep '^GWTEXVAR[[:space:]]*=[[:space:]]*\\\ 
> $VARTEXMF' \"${previoustexmfcnf}\" >/dev/null 2>&1") != 0) {
> 	    setHomeTeXUse( 0);
> 	}
> 	else {
> 	    setHomeTeXUse( 1);
> 	}
>     }
> }

and this parameter is then used in the script tex.sharedscript.pm to  
decide whether to set GWTEXVAR to $VARTEXMF (blocking personal  
configurations) or $HOMETEXMF (de-blocking them):

> sub setHomeTeXUse
> {
>     my $hometexuse = shift;
>     my $texmfcnf = "${II2INSTALLDIR}/texmf.cnf";
>
>     open( TEXMFCNF, "<${texmfcnf}") or die "### ${PROGNAME}: Cannot  
> open $texmfcnf for reading}\n";
>     my @texmfcnfarray = <TEXMFCNF>;
>     close TEXMFCNF;
> #    print "\n%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%\n";
> #    print @texmfcnfarray;
> #    print "\n%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%\n";
>     open( TEXMFCNF, ">${texmfcnf}") or die "### ${PROGNAME}: Cannot  
> open $texmfcnf for writing}\n";
>     foreach my $line (@texmfcnfarray) {
> 	if ($hometexuse) {
> 	    $line =~ s/^\s*GWTEXVAR\s*=.*/GWTEXVAR=\$HOMETEXMF/;
> 	}
> 	else {
> 	    $line =~ s/^\s*GWTEXVAR\s*=.*/GWTEXVAR=\$VARTEXMF/;
> 	}
> 	warn $line;
> 	print TEXMFCNF $line;
>     }
>     close TEXMFCNF;
> }

At least that what I've understood. There may be more subtle issues  
involved, but I've no longer time available for that kind of stuff.

Bruno
------------------------- Helpful Info -------------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
TeX FAQ: http://www.tex.ac.uk/faq
List Archive: http://tug.org/pipermail/macostex-archives/
List Reminders & Etiquette: http://www.esm.psu.edu/mac-tex/list/