Date: Mon, 19 Aug 2013 23:42:51 +0200 From: Roland Smith <rsmith@xs4all.nl> To: Aymeric Mansoux <aymeric@kuri.mu> Cc: freebsd-questions@freebsd.org Subject: Re: Tex Live vs. print/texlive-full (was Re: texlive and package updating) Message-ID: <20130819214251.GA45729@slackbox.erewhon.net> In-Reply-To: <5876de2d649be35ec512c92fd5f0d8c9.squirrel@kokonatsu.kuri.mu> References: <20130809123643.1b6f7fb6@scorpio> <52051B6A.30209@tundraware.com> <5206644C.6060803@riseup.net> <5876de2d649be35ec512c92fd5f0d8c9.squirrel@kokonatsu.kuri.mu>
next in thread | previous in thread | raw e-mail | index | archive | help
--/04w6evG8XlLl3ft Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 16, 2013 at 08:43:13AM +0200, Aymeric Mansoux wrote: > Hello, >=20 > On Sat, August 10, 2013 6:03 pm, Nikola Pavlovi=C4=87 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=20 Same here. I generally don't update TeX more than once a year, which works fine for me. > >> 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? My solution to this problem was to maintain my own patches for ports that I used that relied on TeX. These patches would point to the relevant binaries without adding dependencies. I would apply these patches after running port= snap and before running portmaster. Luckily, TeXLive pretty much has everything TeX-related you'll ever need. A= nd after switching from emacs to vim, I also don't need auctex anymore. Other ports have made TeX an optional dependency. Currently none of the ports tha= t I use require TeX. > > 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). >=20 > 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: > http://www.tug.org/texlive/quickinstall.html Those instructions pretty much cover what you have to do. I add the path to the TeXLive binaries in /etc/login.conf instead of in one= of the shell rc files. And since I like using TeX fonts, I added the directori= es for e.g. the tex-gyre fonts to the GS_FONTPATH environment variable, so that ghostscript can find them if necessary. Roland --=20 R.F.Smith http://rsmith.home.xs4all.nl/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --/04w6evG8XlLl3ft Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iEYEARECAAYFAlISkVsACgkQEnfvsMMhpyUcAwCeJx9ERGwh8scDyNItSTQfN5+b B3IAnjoDOJMf96bmhV4KIm+FO+UmkRVH =V3sc -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130819214251.GA45729>