[gentoo-portage-dev] Re: "official way" for setting per package CFLAGS and FEATURES?

[Duncan <1i5t5.duncan@cox.net>]

Zac Medico <zmedico@gentoo.org> posted 4A638016.3040602@gentoo.org,
excerpted below, on  Sun, 19 Jul 2009 13:20:38 -0700:

> Pacho Ramos wrote:
>> Hello, I would want to always merge xorg-server, libdrm, and  intel
>> driver (that likes to crash a lot) to be always compiled with debugging
>> symbols and FEATURES="${FEATURES} splitdebug"

> I use pre_pkg_setup hooks defined in /etc/portage/env.

Does /etc/portage/env work for the python part of portage yet, or just 
the ebuild.sh layer?

Either way should work for the above (and I too use it regularly for 
CFLAGS, etc), but if the python components don't see it, it won't work 
for dependency checking, fetching, FEATURES used by emerge itself not the 
ebuild.sh callout, etc.  IIRC that used to be a limitation, but I'm not 
sure it still applies.

(Also, as I've seen it explained, the reason it's not better documented 
is deliberate, because there's no standard way to include env file 
contents in reports such as emerge --info for bug reports and the like.  
Without that, many devs are reluctant to have it widely known due to the 
bug squashing problems its likely to cause, so it remains a semi-secret, 
known mainly by the Gentoo power users, who hopefully know to report its 
use when it applies.  If you check bugs I've filed, for instance, say for 
parallel make aka MAKEOPTS, you'll note that I often mention that I 
verified that MAKEOPTS=-j1 works by setting it in the appropriate env 
file.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman