The TeXLive installer gives users on Unix-like systems (I use Debian Stable) the option to install symbolic links in the /usr/local/bin directly for the TeX executables (tex, pdflatex, pdfcrop, cweave, and many others).
Doing so has the positive effect that the user does not need to change any environmental variables to run TeX, since, /usr/local/bin is already in the system's search path. The disadvantage is that this requires one to install as root, which can create security problems and makes it harder to adjust the distribution; and it puts files in an important system directory rather than keeping the distribution contained inside /usr/local/texlive.
When I install the new year's distribution, I do not want to use the symbolic links again; it seems simpler now to add the path manually.
How, then, can I remove the symbolic links from the previous year's installation that are still in /usr/local/bin? Can I do this through last year's installer, perhaps?
(I would also appreciate comments regarding the benefits or problems of using the symbolic links, though I know that is opinion-based. Also, I realize the technical content of the question might be better suited to the Unix-Linux Stackexchange, but it seemed to me this was a question that should be on this site as many TeX users are likely to encounter it.)
(cd /usr/local/bin; ls -l) | grep '^l.*/usr/local/texlive/bin/' | sed 's/^.*2014 \([a-zA-Z0-9\-\_]*\) \->.*$/\1/'should give you a list. – cfr Jul 25 '15 at 20:48/usr/local/texlive/2014/bin/and this didn't catch all the filenames with special characters, so I had to fiddle with it a bit. This worked to make a list of file names:(cd /usr/local/bin; ls -l) | grep '^l.*/usr/local/texlive/2014/bin/' | sed 's/^.* \([a-zA-Z0-9\+\.\_\CHAR-]*\) \->.*$/\1/' > /tmp/texlinks.txt– musarithmia Jul 25 '15 at 21:28(cd /usr/local/bin; ls -l) | grep '^l.*/usr/local/texlive/2014/bin/' | sed 's/^.* \([^ ]*\) \->.*$/\1/' > /tmp/texlinks.txtbut check the output carefully if you use this! – cfr Jul 25 '15 at 21:32sudo xargs -rd '\n' --arg-file=/tmp/texlinks.txt rm -i --(From this answer). – musarithmia Jul 25 '15 at 21:39info, you should not just delete the links but delete them from the database, too. In the case ofmanthis should probably happen automatically, possibly with some delay depending on your configuration. – cfr Jul 25 '15 at 22:04/etc/paths.d(for setting the path for all user). One file is much better than tens of them;-)and, moreover, one can easily arrange things so the you don't even have to replace that file at any upgrade. – egreg Jul 25 '15 at 22:04/etc/paths.da Mac OS X thing? Certainly it is not generally available on GNU/Linux systems. (I don't have it and that is not how I add to PATH on my machines.) – cfr Jul 25 '15 at 22:21/usr/local/bin, it is important that this directory is not intended to be used for system files in the sense that it is not managed by your distro's package manager. You should be able to delete everything in/usr/localwithout upsettingapt, for example. So this is very different from, say, installing links into/usr/binwhich would be poking things into areas which your package manager expects to manage itself. (Sometimes, there are still reasons to do it, but not lightly.) – cfr Jul 25 '15 at 22:24/etc/paths.dis also a Debian thing. – egreg Jul 26 '15 at 05:44