On 26 Jan 2009, at 22:51, Grant wrote:
...
So for example, miro needs xine to play videos. If I ./configure miro
with --prefix=/usr/local, it will install to /usr/local/miro or
similar?
Yes. Read the configure options for the app you're installing. It
might also have a --libprefix or similar that you need to change, too.
Then I would need to point it to xine and possibly others
since it wasn't configured like --prefix=/ ?
Usually the configure scripts should find stuff installed in the main
part of the system.
Is all this done as root?
`./configure && make` as user, `make install` as root (sudo?).
... in any case
save the source tree for further refference, or just to be able to
make
uninstall.
Couldn't I just uninstall with 'rm -rf /usr/local/miro' ?
I don't know about miro, but often foo will install not install a
directory /usr/local/foo but instead files /usr/local/food & /usr/
local/foobar. These will get "intermingled" with files /usr/local/bard
& /usr/local/barfoo, so `make uninstall` is used to uninstall the
files cleanly.
I believe that configure scripts for some programs (e.g. mplayer?) may
also sometimes install config files in /etc - I think `make uninstall`
will remove these, but I get the impression from your earlier posts
that you may find this undesirable.
Nevertheless, it is worth experimenting with compiling by hand using
this method - I would consider it an essential Linux skill and it will
give you an insight into things around which Portage is merely a
wrapper.
Stroller.
