On Wed, 2006-06-07 at 16:05 -0400, Alec Warner wrote: > We've discussed this multiple times, and it's always been the conclusion > that per package.env should go in bashrc, as bashrc is generally more > powerful than anything we could devise. The only downside afaik, for > bashrc is that you can't do per package FEATURES as FEATURES is a > python-side var. But you shouldn't need per package FEATURES by design; > FEATURES are for portage, not your ebuild.
This is a thumbs up? I've got the code sitting in my $PORTDIR/profiles/base/profile.bashrc to give us just this. I'd be all to happy to commit it. So that's a yes right? :) -- Ned Ludd <[EMAIL PROTECTED]> Gentoo Linux -- firstname.lastname@example.org mailing list