Gentoo Archives: gentoo-dev

From: Alec Warner <antarus@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] fix binary debug support, part elevenity billion + 1
Date: Wed, 07 Jun 2006 23:17:56
Message-Id: 44875D48.3030203@gentoo.org
In Reply to: Re: [gentoo-dev] fix binary debug support, part elevenity billion + 1 by Ned Ludd
1 Ned Ludd wrote:
2 > On Wed, 2006-06-07 at 16:05 -0400, Alec Warner wrote:
3 >
4 >
5 >>We've discussed this multiple times, and it's always been the conclusion
6 >>that per package.env should go in bashrc, as bashrc is generally more
7 >>powerful than anything we could devise. The only downside afaik, for
8 >>bashrc is that you can't do per package FEATURES as FEATURES is a
9 >>python-side var. But you shouldn't need per package FEATURES by design;
10 >>FEATURES are for portage, not your ebuild.
11 >
12 >
13 >
14 > This is a thumbs up? I've got the code sitting in my
15 > $PORTDIR/profiles/base/profile.bashrc to give us just this.
16 > I'd be all to happy to commit it. So that's a yes right? :)
17 >
18 >
19
20 As I told you on IRC, it's not your job to listen to the portage devs on
21 this one, you know what was intended for that support, we've argued
22 over it a dozen times. There is nothing we can do to stop you from
23 "mis-using" something in portage, aside from complaining and removing it
24 in the next version. I believe we have made our recommendation and you
25 know what we think you should do, but we are not Gentoo.
26
27 I would be more concerned with convincing the rest of the developers.
28 adding crap in base profile.bashrc will affect 99% of users, so it
29 better be friggin correct and useful, otherwise you will piss a ton of
30 people off.
31 --
32 gentoo-dev@g.o mailing list

Replies