On Tue, May 01, 2007 at 07:28:06PM +0200, Paul Sebastian Ziegler wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hy everybody,
>
> can you please tell me if there is some way to set the install directory
> of an ebuild globally without changing the ebuild?
> Let me clarify:
> I want a few packages to not be merged under / directly but rather to be
> located under /something/*.
> I understand that the ebuilds contain directives of where to install the
> files through src_install(). However I don't believe it would be a good
> idea to edit ebuilds manually since it would lead to breakages during
> emerge --sync.
> So is there some file I can edit to change the install directory for a
> certain package?
> For example like setting
> wireshark /wifi
> firefox /stuff
> baselayout /
> (this is just a rough sketch of what I'm looking for.)
>
> All help would be greatly appreciated!
>
> Many Greetings
> Paul
As far as I know there is no way to change the prefix via portage, since its
all hardcoded (kinda makes me wonder why this was never added as a feature
tho). My best guess is that you're going to have to setup an overlay. This is
what I would do (untested tho):
copy any ebuilds to /usr/local/portage/{category}/{app}/whatever.ebuild
rename that ebuild so its version number is really high (like 99999) so portage
will default to it instead.
change the prefix in the ebuild
Install via emerge. I don't think I've ever seen anything in stable with a
version number that high, so as long as you make sure that the ebuild is in the
stable tree and you're not using unstable packages it *shouldn't* ever emerge
over it. Down side is you will have to do this everytime you want to update
the package.
Kinda a halfass way to do it, but I think it would work.
-Rick
--
[EMAIL PROTECTED] mailing list
