5 ms·
Stuff compiled from source should not be installed to the same prefix as stuff provided by the OS and/or package manager. For programs that use the de-facto st
by jey 17y ago
Stuff compiled from source should not be installed to the same prefix as stuff provided by the OS and/or package manager.
For programs that use the de-facto standard GNU Autocrap build system you can specify this by passing "--prefix=/usr/local" to the "./configure" script. It's also good to not install everything system-wide, and instead have a $HOME/bins prefix, with $HOME/bins/bin added to PATH. (And $HOME/bins/lib to LD_LIBRARY_PATH, and that pkg-config thing if it matters, etc)
- rbanffy 17y agoAgreed. I had some problems long ago that may have burned me a little. It was pointed out that should be no problem most of the time. But why did you call it "GNU Autocrap build system"?
- blasdel 17y agoFreeBSD takes this a radical step further -- its package system only ever installs things to /usr/local. Your own random shit needs a third prefix. It won't even make a /bin/bash -- unless you fuck shit up, everything outside of /usr/local /home and /root came directly from the FreeBSD project, period. You can checkout the source to your system's entire userland from one repository, and build it with one make. I wish there was a nice Linux distro that held itself to this. Gentoo makes a nice distinction in portage between the necessary system packages that come built in the tarball and the world packages that you installed and care about, but it mixes them together in the filesystem.