On Fri, Aug 16, 2013 at 08:43:13AM +0200, Aymeric Mansoux wrote:
Hello,
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
Same here. I
Hello,
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
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: h...@freebsd.org
With: TEX_DEFAULT=texlive placed in the /etc/make.conf file.
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
Port: texlive-full-20120701
Path: /usr/ports/print/texlive-full
Info: TeX Live, Full Version
Maint: h...@freebsd.org
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
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: h...@freebsd.org
With: TEX_DEFAULT=texlive placed in the /etc/make.conf file.
My question is how do I update the packages since the package updater
