Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Aug 2013 08:43:13 +0200
From:      "Aymeric Mansoux" <>
Subject:   Tex Live vs. print/texlive-full (was Re: texlive and package updating)
Message-ID:  <>
In-Reply-To: <>
References:  <20130809123643.1b6f7fb6@scorpio> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

On Sat, August 10, 2013 6:03 pm, Nikola Pavlović wrote:
> On 09/08/13 18:40, Tim Daneliuk wrote:
>> I've given up on all OS distribution-based TexLive drops.  I install
>> texlive manually from their installer and then run tlmgr under
>> cron control nightly to keep it up-to-date.  I do this on
>> FreeBSD (my primary dev and server platform) as well as all
>> linux instances in my environment.  It makes things a lot simpler.
> How do you manage dependency tracking errors?  The last time I've
> installed it the way you do was on Slackware and since it doesn't do any
> dependency tracking there were no problems (as long as the binaries were
> in PATH).  I can imagine ports and pkg tools on FreeBSD complaining
> about missing TeX packages, and AFAIK Debian based Linux distributions
> will certainly complain (I think there is a workaround, but it involves
> messing with dpkg).

I am also curious about this one. Any guideline or special considerations
regarding the use of the Tex Live distribution straight into FreeBSD would
be very helpful. Or is it just a matter of following this:

While previous texlive-full port seemed to work fine. I haven't been able to
install it on new machines as it seems something is wrong with
not able to figure out where kpathsea and zlib are, or something like that.
It feels that it is stuck in some sort of transition between few ports to
ports to provide Tex Live in the Collection (speculating...).

Any feedback on this would be appreciated!

Want to link to this message? Use this URL: <>