Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Aug 2013 10:41:18 -0400
From:      Jerry <>
To:        FreeBSD <>
Cc:, Tim Daneliuk <>,
Subject:   Re: texlive and package updating
Message-ID:  <20130810104118.7b1c6618@scorpio>
In-Reply-To: <>
References:  <20130809123643.1b6f7fb6@scorpio> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Fri, 09 Aug 2013 11:40:10 -0500
Tim Daneliuk articulated:

> On 08/09/2013 11:36 AM, Jerry wrote:
> > Port:   texlive-full-20120701
> > Path:   /usr/ports/print/texlive-full
> > Info:   TeX Live, Full Version
> > Maint:
> >
> > With: TEX_DEFAULT=texlive placed in the /etc/make.conf file.
> >
> > My question is how do I update the packages since the package
> > updater has apparently been deliberately disabled? I install/update
> > dozens of packages each week on my Windows machine, so I know that
> > they are available.
> >
> > Also. all of the "*-freebsd-doc-*" ports are bonked due to the
> > use of "texlive". Is there any headway being made on that front?
> 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.

I have to admit that I am somewhat confused myself. Why the port was
released sans any viable method of updating the packages seems counter

I know for a fact that this problem does not exist on an MS Windows
machine, nor from what I have been able to ascertain, most other *.nix
operating systems. Hopefully these two glaring problems will be
rectified soon.

I am wondering if I simply make "tlmgr" operational, if it will work.
Did you have to do anything special to accomplish getting "tlmgr"
working and updating correctly?

Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.

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