Alexander Hansen wrote: [] > How to make sure your TeX distro's executables get used depends on where > it puts them. You may be able to do this in your .profile (or whichever > startup preference file you're using) like this example: > > . /sw/bin/init.sh > export PATH=/usr/local/bin:$PATH > > which assumes your TeX distro uses /usr/local/bin for its executables.
Mostly it is now /usr/texbin. I once advised to create a file texlive.sh in /sw/etc/profile.d/ containing the path prepending command for /usr/texbin, so that it would be executed automatically when the Fink environment is loaded. But in the meantime it has turned out this this was not such a good idea. The problem was that when Fink is building packages, it needs to use its own commands from the texinfo package, such as texi2html and makeindex, and not those in /usr/bin/ from OSX nor in /usr/texbin/ nor /usr/local/bin/ from another tex distribution. If you prepend /usr/texbin in your own ~/.profile script, I think it will be OK, because fink will not see this; it only uses the environment loaded by /sw/bin/init.sh for its own building environment. Prepending /usr/local/bin might be necessary, too, but it should be done with extreme care, because /usr/local/bin is a general garbage dump, and it might produce unwanted surprises. -- Martin ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Fink-beginners mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.beginners
