Re: SVN tex-common commit: r1695 - tex-common/trunk/scripts
On Sat, Oct 07, 2006 at 19:15 +0200, Florent Rougon wrote:
> Ralf Stubner <ralf.stubner@web.de> wrote:
>
> > Now as long as the admin does not alter the search path, a file in
> > /usr/share/texmf/web2c does no harm.
>
> OK, but _it_ _should_ _not_ _be_ _there_. :)
ACK
> So, I don't see any harm if we bail out when finding such a file, unless
> of course you're 100% sure we won't find any "broken" installation with
> a bad file in usr/share/texmf/web2c...
I don't think one can be 100% sure if one is outside the regime of logic
and mathematics. But I do find it rather unlikely that we will still
find any /usr/share/texmf/web2c/updmap.cfg now, since update-updmap
checked for this location for quite some time. And since Nov 2005 using
one of the bad options would create /etc/texmf/web2c/updmap.cfg. So we
would need a unstable user who hasn't updated for about a year. I am not
sure how likely that is.
> But I admit it is just a refinement, a safety net to ensure the various
> TeX upgrades went fine.
Could /usr/share/texmf/web2c/updmap.cfg get generated during an update?
I know only two possibilities: The admin places there on purpose (for
whatever reason) or one of the 'bad options' was used when
TEXMFSYSCONFIG was still /usr/share/texmf/web2c. Any other
possibilities?
cheerio
ralf
Reply to: