-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I thought about that too, but wouldn't that more or less create a new "system". For instance if I emerged a library (say libpcap) with ROOT="/libs" and then tried to emerge wireshark (which depends on libpcap) with ROOT="/analysis" I think that wireshark would fail to start due to "missing" libraries. (Or it would pull in libpcap once more and merge it into /analysis thus resulting in several installed copies at once).
Please correct me if I should be mistaken. Thanks for the help Paul Joshua Doll schrieb: > Would ROOT="" in the emerge command work? > > --Joshua Doll > > > Paul Sebastian Ziegler wrote: > 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGN4B6aHrXRd80sY8RCg0fAJ41Oa2OFoXAtZXC0x1upa5L/v96mwCg+pFL FbaXM7poUpNFgJ/g0iGwXpE= =0PAB -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
