Bug 380333 – sys-apps/portage: ignores FEATURES set in /etc/portage/env/${CATEGORY}/${PN} bashrc

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Toralf Förster 2011-08-23 07:55:16 UTC]

I removed from /etc/make.conf the USE flag "test", set this in /etc/make.conf:
FEATURES="parallel-fetch ccache compress-build-logs test"
and  this in /etc/portage/env/sys-power/iasl:
FEATURES="parallel-fetch ccache compress-build-logs"

nevertheless portage wants now rebuild iasl with this command:

emerge --keep-going --nospinner --changed-use --update --ask --deep --tree --with-bdeps=y @world

My problem is, that at one side the USE flags description advice to remove the USE flag from make.conf and to use the FEATURES variable instead. But now I cannot deeply rebuild @world anymore b/c portage wants to iasl (and its test always failes) ...

:-(

Reproducible: Always

[Comment 1 Zac Medico 2011-08-25 16:48:24 UTC]

Don't use bashrc for per-package variables. Since portage-2.1.9.24 we have package.env for this purpose. For example, set "sys-power/iasl notest.conf" in /etc/portage/package.env, and set FEATURES="${FEATURES} -test" in /etc/portage/env/notest.conf.

[Comment 2 Toralf Förster 2011-08-25 17:07:57 UTC]

(In reply to comment #1)
> Don't use bashrc for per-package variables. Since portage-2.1.9.24 we have
> package.env for this purpose. For example, set "sys-power/iasl notest.conf" in
> /etc/portage/package.env, and set FEATURES="${FEATURES} -test" in
> /etc/portage/env/notest.conf.
cool- I assume, similar is true for CFLAGS (b/c I compile only few didicates packages with debug info). ?

[Comment 3 Zac Medico 2011-08-25 17:19:27 UTC]

Yes, CFLAGS and any other variables that you would set globally in make.conf.

[Comment 4 Toralf Förster 2011-08-25 17:30:13 UTC]

(In reply to comment #3)
> Yes, CFLAGS and any other variables that you would set globally in make.conf.
thx, so it is fixed.