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? — The preceding unsigned comment was added by Pygospa (talk • contribs)

says:
 * Depends on personal preferences. But describing it as a "file only" as in this article seems indeed wrong.

etc/portage/ Files in this directory including make.conf, repos.conf, and any file with a name that begins with "package." can be more than just a flat file. If it is a directory, then all the files in that directory will be sorted in ascending alphabetical order by file name and  summed together as if it were a single file.

--Charles17 (talk) 11:10, 4 August 2017 (UTC)

entries starting with <=, = and (=> or nothing) operators
Shouldn't these apparent operators be documented here? --necktwi (talk) 11:20, 2 September 2018 (IST)


 * The referenced "operators" are nowhere to be found in this article. Your complaint is a non sequitur. --Davidbryant (talk) 15:41, 29 July 2020 (UTC)

emerge --info not showing changes from package.env
State somewhere that changes from package.env are not shown when using See bug: https://bugs.gentoo.org/410069


 * The following section has been added in order to address the above concern: Special:Diff/1037442/1044057. --Maffblaster (talk) 22:59, 20 January 2022 (UTC)

crossdev requires package.env to be a directory instead of file
The package, at least on version 20220818 (sys-devel/crossdev-20220818), requires to be a directory.

I had it as a file and after emerging the package i got the following error:
 * error: please convert //etc/portage/package.env to a directory

I haven't edited the page directly because I don't see a specific place to add such a comment and some modifications to the structure of the page may be in order. --Patomas (talk) 10:35, 1 October 2022 (UTC)


 * That's a good thing to know when setting up the package.env config - thanks. Feel free to add the info to the article, even if it needs a little structural change ;). Some articles have a "tips" section, many have "troubleshooting", though glancing at it, maybe the info could go in a subsection "caveats", if not elsewhere. In any cast, thanks for the heads up!! -- Ris (talk) 15:23, 1 October 2022 (UTC)


 * Added this to caveats section. -- Ris (talk) 13:54, 17 November 2022 (UTC)