From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Installing outside of Portage & cruft removal
Date: Tue, 27 Jan 2009 14:34:47 -0800 [thread overview]
Message-ID: <49bf44f10901271434h3c438795i9a12b6b3e1f4011@mail.gmail.com> (raw)
In-Reply-To: <e445d4010901270729x1edefdd7u80d134c4fdeaa715@mail.gmail.com>
> If you are installing a package by hand and wants to revert back to
> the previous state, best is to :
>
> - when you ./configure it, use the various --prefix directives (do a
> ./configure --help for information on that)
> - when you want to remove, make uninstall in the source dir (so don't
> remove it!)
> - if it does not have a remove, usually if you install it inside
> /home/${username}/whatever, then removing that is fine.
>
> Best thing though is to write an ebuild and then Portage will sandbox
> the build so it knows every file that has been installed.
>
> The package knows where to link to when it goes into the ./configure
> stage and won't act like windows, installing stuffs into registry or
> the like ... everything's nicely contained inside /lib and /share
> folders (except /etc files ...which you can safely ignore them there -
> those are just text files and you'll know where they are anyway if you
> intend to configure miro)
Thanks everyone. I've never been open to manual compile/installation
but I can give it a try now.
- Grant
next prev parent reply other threads:[~2009-01-27 22:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 16:41 [gentoo-user] Installing outside of Portage & cruft removal Grant
2009-01-26 16:48 ` Mike Kazantsev
2009-01-26 17:08 ` Jesús Guerrero
2009-01-30 18:45 ` b.n.
2009-01-26 17:35 ` Grant
2009-01-26 17:57 ` Mike Kazantsev
2009-01-26 23:17 ` Neil Bothwick
2009-01-26 17:57 ` Dale
2009-01-26 18:17 ` Grant
2009-01-26 18:26 ` Dale
2009-01-26 19:25 ` Paul Hartman
2009-01-26 20:21 ` Grant
2009-01-26 18:02 ` Rumen Yotov
2009-01-26 18:29 ` Daniel Pielmeier
2009-01-26 20:17 ` Grant
2009-01-26 20:24 ` Jesús Guerrero
2009-01-26 20:30 ` Grant
2009-01-26 20:44 ` Paul Hartman
2009-01-26 20:45 ` Paul Hartman
2009-01-26 20:51 ` Jesús Guerrero
2009-01-26 22:51 ` Grant
2009-01-27 14:29 ` Stroller
2009-01-27 15:29 ` Hieu, Luu Danh
2009-01-27 22:34 ` Grant [this message]
2009-01-27 22:57 ` Paul Hartman
2009-01-26 20:44 ` Daniel Pielmeier
2009-01-26 22:31 ` Grant
2009-01-26 19:57 ` Jesús Guerrero
2009-02-15 20:49 ` Alex Schuster
2009-02-16 18:33 ` Grant
2009-02-16 18:41 ` Dirk Heinrichs
2009-02-16 20:31 ` Grant
2009-02-16 20:40 ` [gentoo-user] " Nikos Chantziaras
2009-02-16 20:48 ` Dirk Heinrichs
2009-02-16 20:54 ` Nikos Chantziaras
2009-02-16 21:09 ` Dirk Heinrichs
2009-02-17 18:22 ` Grant
2009-02-17 18:35 ` Dirk Heinrichs
2009-02-16 20:43 ` [gentoo-user] " Dirk Heinrichs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49bf44f10901271434h3c438795i9a12b6b3e1f4011@mail.gmail.com \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox