| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 15/06/14 16:13, John Campbell wrote: |
| 5 |
> On 06/14/2014 10:10 PM, Dale wrote: Yes, you can skip the version number. |
| 6 |
> It should be just like the package.* directories but for env(ironment) |
| 7 |
> variables. It wouldn't suprise me if someone renamed it to package.env |
| 8 |
> someday like they did from package.keywords to package.accept_keywords. |
| 9 |
|
| 10 |
*I* could be wrong, but this looks wrong. |
| 11 |
|
| 12 |
The way I understand the environment overrides to work is: |
| 13 |
|
| 14 |
You create a file in /etc/portage/env with your environment overrides: |
| 15 |
|
| 16 |
file /etc/portage/env/notmpfs.conf: |
| 17 |
PORTAGE_TMPDIR="/var/tmp/portage-notmp" |
| 18 |
|
| 19 |
You then instruct which packages are to use a given environment override using |
| 20 |
package.env: |
| 21 |
|
| 22 |
file /etc/portage/package.env: |
| 23 |
mail-client/thunderbird notmpfs.conf |
| 24 |
|
| 25 |
When emerge begins work on a given atom, it will look at package.env to see if |
| 26 |
there are any environment override directives given, and if so, use the |
| 27 |
variables defined in the specified environment file to override those in |
| 28 |
make.conf (or the default value if not specified). |
| 29 |
|
| 30 |
At least, this is how I use /etc/portage/{,package.}env, and afaik is *how* |
| 31 |
it's supposed to be used (as far as I understand man portage(5)). |
| 32 |
|
| 33 |
Please, feel free to correct me if i'm wrong. |
| 34 |
|
| 35 |
- -wraeth |
| 36 |
-----BEGIN PGP SIGNATURE----- |
| 37 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 38 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 39 |
|
| 40 |
iF4EAREIAAYFAlOdP+wACgkQXcRKerLZ91mPygD/QNgEvnYIwnenijsM1ekj/2Hj |
| 41 |
MvvHHojrdWHg4JudKAMA+wexTE9z9JEAYQRZARQS1NSd2sQj637cTpVl18NDE2BD |
| 42 |
=vWhf |
| 43 |
-----END PGP SIGNATURE----- |
Archives