Date: Mon, 16 Sep 2013 07:59:32 -0400 From: Jerry <jerry@seibercom.net> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: Getting tlmgr working Message-ID: <20130916075932.4a2c420a@scorpio> In-Reply-To: <20130916062609.GA72029@slackbox.erewhon.net> References: <20130915180403.1bd21579@scorpio> <20130916062609.GA72029@slackbox.erewhon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/4qZHXN/syL30J9/d7MCXA6y Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, 16 Sep 2013 08:26:09 +0200 Roland Smith articulated: > On Sun, Sep 15, 2013 at 06:04:03PM -0400, Jerry wrote: > > Has there been any movement on getting "tlmgr" working on FreeBSD? > > The inability to get and install updates is annoying. >=20 > Basically there are two ways of dealing with TeXLive; >=20 > 1) Install it from ports. This also means using ports to update it. > 2) Use the TeXLive installer to install it. In this case you can use > tlmgr to update it. >=20 > I've used method 2 since 2007, and that has worked fine for me. The problem is that the ports system is not keeping individual TeXLive packages. I primarily use TeXLive on an MS Windows system where it runs faster and is easier to maintain then on FreeBSD. There is an old adage, "If it ain't broke, don't fix it." Unfortunately, in the case of "tlmgr", they failed to pay heed to that advice. The ports system is not keeping individual TeXLive packages updated. Besides, using a big, complex system like the FreeBSD ports system to keep the individual packages of a single program, in this case TeXLive, updated when the program supplies its own mechanism for doing so, is just another failed attempt at reinventing the wheel. As my deceased grandmother would say when she witnessed something incredibly stupid being done, "What the hell were they thinking?" There area also a slew of other ports that fail to install if the system is configured to run TeXLive. When they will get that problem solved is anyone's guess. The bottom line is the port and all of the assorted problems with it and other ports it affects were not resolved prior to its release. At the very least, a nice large warning banner should have been displayed when the port was first installed clearly listing all of the known problems and side effects of the port. However, that is just my 2=C2=A2. --=20 Jerry =E2=99=94 Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ --Sig_/4qZHXN/syL30J9/d7MCXA6y Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iQEcBAEBAgAGBQJSNvKsAAoJEF2rWD2do7dNqiwIAIqCOryzj0ZMsPueZqvJEDJe bSyFu6aNLfAmZojICFiPOZ4bu19Abl4B6OSfBnHSO3IrTnAbBDYKjyAeyVEfJxKx cMZjLBpohXbLFbAQAvmG1sH13rYEabk7VrN55we9d9txvN0gosApiZuUiq+GM9Tj iHvec8K0WEsS9e+L2WL0AU6FvPY+QLnG85EiWs8rUTWpBZzy02Wtcx5qgv7rMDS0 odUFAEzW4n6jGGPKd181PeEWwlioxU4narzVu7oYIdGYweBtQ7HR2PkfQD7c0UQr P6/1pHOMCX/6Y0khzHOH2BoIuj8P0PDRMxKhnYjs89en8jBg3iwS1ljfzp/VCYc= =OaI/ -----END PGP SIGNATURE----- --Sig_/4qZHXN/syL30J9/d7MCXA6y--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130916075932.4a2c420a>