1 |
On Wed, 2006-06-07 at 16:05 -0400, Alec Warner wrote: |
2 |
|
3 |
> We've discussed this multiple times, and it's always been the conclusion |
4 |
> that per package.env should go in bashrc, as bashrc is generally more |
5 |
> powerful than anything we could devise. The only downside afaik, for |
6 |
> bashrc is that you can't do per package FEATURES as FEATURES is a |
7 |
> python-side var. But you shouldn't need per package FEATURES by design; |
8 |
> FEATURES are for portage, not your ebuild. |
9 |
|
10 |
|
11 |
This is a thumbs up? I've got the code sitting in my |
12 |
$PORTDIR/profiles/base/profile.bashrc to give us just this. |
13 |
I'd be all to happy to commit it. So that's a yes right? :) |
14 |
|
15 |
|
16 |
-- |
17 |
Ned Ludd <solar@g.o> |
18 |
Gentoo Linux |
19 |
|
20 |
-- |
21 |
gentoo-dev@g.o mailing list |