Re: Tex Live vs. print/texlive-full (was Re: texlive and package updating)
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 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 portsnap and before running portmaster. Luckily, TeXLive pretty much has everything TeX-related you'll ever need. And 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 that 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). 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 directories for e.g. the tex-gyre fonts to the GS_FONTPATH environment variable, so that ghostscript can find them if necessary. Roland -- 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) pgpbE1eiSZmyE.pgp Description: PGP signature
Tex Live vs. print/texlive-full (was Re: texlive and package updating)
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 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: http://www.tug.org/texlive/quickinstall.html 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 japanese/tex-ptex 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 many ports to provide Tex Live in the Collection (speculating...). Any feedback on this would be appreciated! a. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: texlive and package updating
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. 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 productive. 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. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: texlive and package updating
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). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
texlive and package updating
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 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? -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: texlive and package updating
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 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. - Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
