> > > Another possible feature in the future (not finished thinking about > > > yet) > > > could be to have portage install each (non-system-)package into a > > > separate prefix within its domain, without need to change prefix-api. > > > This could help ebuild-devs to detect unknown dependencies, which are > > > not found implicitly if not specified at configure-line. > > > Well - only for a testing system, and to be enabled explicitly > > > by setting FEATURES. > > > > This probably isn't as crazy as you might think. With ROOT, and a > > little more work on PREFIX, it should just be a matter of setting > > these appropriately on a per package basis. The other possible use > > for this would be creating package bundles with complete dep trees > > suitable for distribution.
> Wow, ideas over ideas, and they all are conceivable! Because we are at strange ideas, would it be possible to introduce something like $PREFIXES, where this is a list of directories, say $PREFIXES=/:/gentoo If I want to emerge a package, the package should be installed into the first matching PREFIX If problems occur, say because there exist a un-manged version of some package, the prefix is black-listed for this packaage, and the next directory is choosen. This black-listing can also be done by a user. So I could emerge (and use), say app-text/editors into PREFIX=/, while, say dev-lan/python is emerged into /gentoo This would leave a problem how the correct executable and / or their corresponding resources are found. Say, imagemagic wants to call /usr/bin/gs, but ghostscript is really installed into /gentoo/usr/bin/gs Regards Dirk -- [email protected] mailing list
