On Wed, Jul 07, 2004 at 01:35:28PM -0500, Min Sik Kim wrote:
> * Julio M. Merino Vidal, Wed, 7 Jul 2004 17:44:08 +0200:
> > [snip]
> > 
> > The last solution, the one I'm proposing, is the following: make each
> > package install itself in its own depot directory.  But, for packages
> > that search for files in shared directories (pkgconfig, in this example),
> > add a patch that changes the path where files are searched.  Instead of
> > hardcoding the path value in the binary, the program should check the
> > value of an env variable (PKG_VIEWBASE) and look for files there.
> > I.e., pkgconfig could use ${PKG_VIEWBASE}/lib/pkgconfig to search its
> > files.  (We'd make it fallback to the default view if the variable is
> > unset).
> 
> I vote for this solution, but have a minor concern.  Many packages
> already have such an env variable (e.g. PKG_CONFIG_PATH of pkgconfig).
> Then wouldn't it be better to use it, instead of adding a patch to
> teach PKG_VIEWBASE, especially when we create wrapper scripts to hide
> PKG_VIEWBASE?
> 
> Other than that, I prefer this solution and I'm willing to help.

Likewise - I like Julio's 3rd solution, and Min Sik Kim's addendum,
and I, too, am prepared to help.

It's nice to see people getting to grips with pkgviews.

Thanks,
Alistair