| 1 |
On Sunday 11 March 2007, Alex Schuster wrote: |
| 2 |
|
| 3 |
> Additionally, I like to have the stuff separated in sub-directories |
| 4 |
> of /usr/local, and use stow or better xstow to create symlinks, so |
| 5 |
> the software appears to be installed directly in /usr/local. |
| 6 |
|
| 7 |
That sounds like an awful lot of work, all for no additional |
| 8 |
benefit. /usr/local is for locally compiled pieces of software, and |
| 9 |
normally one runs 'make uninstall' in the code's src dir to remove it. |
| 10 |
Also, /usr/local is not supposed to have a hierarchy of sub-dir's (a'la |
| 11 |
windows) beneath it per LFS. /opt is a better choice for that. |
| 12 |
|
| 13 |
As Bo and others have mentioned, an ebuild that you create yourself and |
| 14 |
place in a local overlay is by far the best solution, *especially* if |
| 15 |
the package installs just fine with './configure && make && make |
| 16 |
install'. In that case, the ebuild is literally just a few statements |
| 17 |
such as SRC_URI, HOMEPAGE and perhaps a DEPENDS if there are selectable |
| 18 |
configs. You gain all the benefits of stow plus all the benefits of |
| 19 |
portage, including emerge -C to remove the package from the system |
| 20 |
|
| 21 |
Try it, it's WAY easier than most folk think it is |
| 22 |
|
| 23 |
alan |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
Optimists say the glass is half full, |
| 28 |
Pessimists say the glass is half empty, |
| 29 |
Developers say wtf is the glass twice as big as it needs to be? |
| 30 |
|
| 31 |
Alan McKinnon |
| 32 |
alan at linuxholdings dot co dot za |
| 33 |
+27 82, double three seven, one nine three five |
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives