Talk:/etc/portage/package.env

Setting FEATURES on specific packages
I might be wrong, but I think that the env files only "add" stuff to the default configs. If so, it should be stated in the article.

My case is: I have enabled ccache and distcc in my. Now, if I want to disable ccache and distcc for virtualbox (the compilation notoriously fails with them...), I think it works only when I specify

Initially, I have put, to clear the FEATURES flag, but it didn't work. — Preceding unsigned comment added by Kupusc (talk • contribs) 05:18, March 7, 2016‎


 * Hi, I can look into this. I need to enhance my Portage skillz anyway. I'll close the discussion when I find the answer. Also, please remember to sign your comments on discussion packages. The button is in the formatting box. Kind regards, --Maffblaster (talk) 20:06, 7 December 2016 (UTC)


 * Have an answer! It should work on a per-package basis but be aware the FEATURES variable is an incremental variable, meaning if it's already specified in then Portage will read the values from the  definition, and then read the values from the  file/directory. In other words if   in, and   in , then Portage sees FEATURES set to   at emerge time. This ultimately results in ccache and distcc being disabled, as you intend. Hopefully that makes sense. --Maffblaster (talk) 23:00, 5 January 2017 (UTC)

Directory instead of file
Shouldn't  be rather used as directory with modular files for every package inside, instead of being one big file with a list of all packages?