On Wed, 2004-09-08 at 22:26, Robin H. Johnson wrote:
> On Wed, Sep 08, 2004 at 09:51:15PM -0400, Travis Tilley wrote:
> > Daniel Goller wrote:
> > >although i am against overly tweaking CFLAGS, someone suggested 
> > >something that might be more sane to ask for:
> > >
> > >/etc/portage/packages.cflags
> > >
> > >an easy way to maintain your cflags you worked so hard for to obtain, 
> > >you can trade them in the forums or ebay and then append to your file, 
> > >not much work to implement in my eyes, and all the testing work is done 
> > >by those who want it
> > mkdir /etc/portage and copy this file there (MUCH thanks to solar for 
> > writing this. he like... kicks ass an stuff). it implements an 
> > /etc/portage/package.cflags without needing to patch portage. i think 
> > this might require portage 2.0.51_pre... no idea, i havent used 2.0.50 
> > in a while.
> [snip]
> Could this be generalized to do /etc/portage/package.env like somebody
> else asked for?
> 
> And then simply put a CFLAGS line in the file referenced by package.env,
> as it seems that it really would belong there.

I played with that idea for a few mins, but unfortunately I found no
easy way in bash to deal with the quotes.
Assuming this syntax.

sys-apps/paxctl CFLAGS="-Os -fomit-frame-pointer" 
sys-devel/gdb CFLAGS="-O2 -g3"
app-misc/beep FEATURES="sfperms sandbox" LDFLAGS="-Wl,-z,now
-Wl,-z,relro"
dev-libs/openssl CFLAGS="-O3 -fno-omit-frame-pointer -m32"
..

Maybe somebody else is motivated to do it from the basic idea. I gave up
and settled for the easy way out of package.cflags package.ldflags here
locally.

-- 
Ned Ludd <solar@gentoo.org>
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer