On Thu, 2006-01-26 at 21:27 -0600, Kito wrote:
> On Jan 26, 2006, at 11:10 AM, Michael Haubenwallner wrote:
>
> > The idea is to substitute this with a bash-function, echoing a prefix.
> >
> > This function could be defined to get one argument, which is much like
> > the same syntax as the *DEPEND settings, but only for a single
> > package.
> > If no argument, the current package is used.
> >
> > Yes, the current implementation would be simple:
> > prefix() {
> > echo $PREFIX
> > }
> >
> > But the idea behind that is:
> >
> > Once portage could handle interdomain dependencies, the prefix-api
> > need
> > not to be changed to let ebuilds find the prefix of their
> > dependencies.
>
> So really, portage needs to imitate pkgconfig on some level, probably
> just start by looking in the vdb, shouldn't be too hard in a single
> domain/vdb situation. The interdomain bit is going to depend on many
> factors unknown to me, and not something we should pursue in the
> current 2.x codebase, but I assume saviour has at least the entry
> points to make this possible.
Sure, not in 2.x, just to be prepared.
>
> >
> > 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!
-haubi
--
[email protected] mailing list
