Archives
Archives
| From: | "Michał Górny" <mgorny@g.o> | ||
|---|---|---|---|
| To: | Bertrand Simonnet <bsimonnet@××××××.com> | ||
| Cc: | gentoo-portage-dev@l.g.o | ||
| Subject: | Re: [gentoo-portage-dev] [PATCH] per package environment: generalize the mechanism to be profile specific | ||
| Date: | Thu, 18 Sep 2014 08:03:22 | ||
| Message-Id: | 20140918100250.4543a789@pomiot.lan | ||
| In Reply to: | Re: [gentoo-portage-dev] [PATCH] per package environment: generalize the mechanism to be profile specific by Bertrand Simonnet |
||
| 1 | Dnia 2014-09-17, o godz. 14:57:10 |
| 2 | Bertrand Simonnet <bsimonnet@××××××.com> napisał(a): |
| 3 | |
| 4 | > I'd rather use the env/ mechanism instead of the package.env one as it is |
| 5 | > more flexible. |
| 6 | |
| 7 | It depends on what you aim to do. As portage(5) points out, both have |
| 8 | their advantages: |
| 9 | |
| 10 | - package.env is parsed early, and so allows you override more |
| 11 | variables, like FEATURES, |
| 12 | |
| 13 | - env/ is used as bashrc extension. |
| 14 | |
| 15 | The other difference is that package.env supports any atom syntax that |
| 16 | the particular EAPI supports, while env/ has hardcoded list of |
| 17 | possibilities. |
| 18 | |
| 19 | -- |
| 20 | Best regards, |
| 21 | Michał Górny |
| File name | MIME type |
|---|---|
| signature.asc | application/pgp-signature |
| Subject | Author |
|---|---|
| Re: [gentoo-portage-dev] [PATCH] per package environment: generalize the mechanism to be profile specific | Bertrand Simonnet <bsimonnet@××××××.com> |