David R. Morrison wrote:
A very practical solution to this problem is: if you run into troubleThere are a handful of packages that need tetex and/or ghostscript for building. This would forbid moving /usr/local/teTeX and /usr/local/bin out of the way if system-tetex or system-ghostscript are installed.
compiling a Fink package, try "sudo mv /usr/local /usr/local.bak" and
then compile the package. Afterwards, you can do "sudo mv /usr/local.bak
/usr/local" to restore things to their original state.
The things most likely to cause interference are in /usr/local/lib and
/usr/local/include. However, there could be problems with things in /usr/local/bin as well, and that's where teTeX (which is harmless) would
be installed.
There is probably no 100% failsafe way of handling possible interactions with things in /usr/local. Moving /usr/local out of the way therefore cannot be made automatic, either.
--
Martin
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
