Gentoo Archives: gentoo-portage-dev

From: Ned Ludd <solar@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] [Bug 44796] Per package environment variables
Date: Fri, 04 Nov 2005 13:31:39
Message-Id: 1131111014.20299.23.camel@localhost
In Reply to: Re: [gentoo-portage-dev] [Bug 44796] Per package environment variables by Brian Harring
1 On Thu, 2005-11-03 at 13:45 -0600, Brian Harring wrote:
2 > On Thu, Nov 03, 2005 at 08:30:26PM +0100, Thomas de Grenier de Latour wrote:
3 > > On Fri, 4 Nov 2005 01:19:35 +0900
4 > > Jason Stubbs <jstubbs@g.o> wrote:
5 > >
6 > > > package.env would be a list of "<atom> <file> [<file> ...]"
7 > > ...
8 > > > With a couple of small modifications to emerge to check FEATURES
9 > > > for "buildpkg" after the call to setcpv() is done rather than
10 > > > doing it once globally, this would also cover TGL's BUILD_PKGS
11 > > > addition too.
12 > >
13 > > Since being able to list several env file on a same line doesn't
14 > > sounds like a must have feature to me, i would much prefer a
15 > > package.env format of that kind:
16 > > <rule> [<rule> ...] <envfile>
17 > > where <rule> would be similar to what i've defined for BUILD_PKGS
18 > > (with addition of full versioned dep atoms, which is a trivial
19 > > change to my code). And if a package happens to match the rules
20 > > lists of several lines, then the corresponding env files would all
21 > > be sourced, in the order of the said lines. I can try to implement
22 > > that if you agree on the idea.
23 >
24 > Offhand, why isn't this a bashrc trick?
25
26 I do this. Works good for me.
27
28 for conf in ${PN}-${PV}-${PR} ${PN}-${PV} ${PN}; do
29 if [[ -f /etc/portage/env/$CATEGORY/${conf} ]]; then
30 . /etc/portage/env/$CATEGORY/${conf}
31 break
32 fi
33 done
34
35 --
36 Ned Ludd <solar@g.o>
37 Gentoo Linux
38
39 --
40 gentoo-portage-dev@g.o mailing list