On Thu, 2005-11-03 at 13:45 -0600, Brian Harring wrote:
> On Thu, Nov 03, 2005 at 08:30:26PM +0100, Thomas de Grenier de Latour wrote:
> > On Fri, 4 Nov 2005 01:19:35 +0900
> > Jason Stubbs <[EMAIL PROTECTED]> wrote:
> >
> > > package.env would be a list of "<atom> <file> [<file> ...]"
> > ...
> > > With a couple of small modifications to emerge to check FEATURES
> > > for "buildpkg" after the call to setcpv() is done rather than
> > > doing it once globally, this would also cover TGL's BUILD_PKGS
> > > addition too.
> >
> > Since being able to list several env file on a same line doesn't
> > sounds like a must have feature to me, i would much prefer a
> > package.env format of that kind:
> > <rule> [<rule> ...] <envfile>
> > where <rule> would be similar to what i've defined for BUILD_PKGS
> > (with addition of full versioned dep atoms, which is a trivial
> > change to my code). And if a package happens to match the rules
> > lists of several lines, then the corresponding env files would all
> > be sourced, in the order of the said lines. I can try to implement
> > that if you agree on the idea.
>
> Offhand, why isn't this a bashrc trick?
I do this. Works good for me.
for conf in ${PN}-${PV}-${PR} ${PN}-${PV} ${PN}; do
if [[ -f /etc/portage/env/$CATEGORY/${conf} ]]; then
. /etc/portage/env/$CATEGORY/${conf}
break
fi
done
--
Ned Ludd <[EMAIL PROTECTED]>
Gentoo Linux
--
gentoo-portage-dev@gentoo.org mailing list
