[tex-live] tl09 release status: coming up

George N. White III gnwiii at gmail.com
Thu Oct 15 04:01:01 CEST 2009

On Wed, Oct 14, 2009 at 10:11 PM, Victor Ivrii <vivrii at gmail.com> wrote:
> On Wed, Oct 14, 2009 at 8:52 PM, Reinhard Kotucha
> <reinhard.kotucha at web.de> wrote:
>>  > There is a rather minimal thing which makes me slightly uneasy with
>>  > TL: assume I need a package which is not in TeXLive, so I install it
>>  > in texmf-local or ~/texmf. Then TL installs this package, so if I want
>>  > to have this package which I use automatically updated, I need to
>>  > remove it from texmf-local or ~/texm. So, I need to be vigilant.
>>  >
>>  > Having few generations of TL with shared texmf-local makes problem worse.
>>  >
>>  > Have anyone found fool-proof solution?

Use texmf-local for stuff that really is site-specific, and create additional
texmf-whatever trees for things that should eventually go in TL,
context-du-jour, etc.

>> Move texmf-local and ~/texmf to the end of the search path in
>> texmf.cnf.
> Thanks, but this solution has prevents me from using say svn version
> of pgf/tikz. I am trying to persuade someone (who is more savvy than
> me) to write texmf-inspector as it would be the only perfect solution.

I think there is some such capability with existing tools, but by using the
multiple extra trees and a bit of diligence it is not a big issue.  In practice
the biggest problem is with users (including application developers) putting
things that belong in texmf trees into the src/doc directories where they
cause problems if you don't use tetex (e.g., the pdftex must produce .pdf
and only .pdf problem).

All these problems will end when the guys from MS show this thread to the
IT bosses and we get a new policy "from now only thou shalt use only the

George N. White III <aa056 at chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia

More information about the tex-live mailing list