| 1 |
On Tue, 2019-11-19 at 22:40 -0800, Zac Medico wrote:
|
| 2 |
> On 11/19/19 2:17 PM, Joakim Tjernlund wrote: |
| 3 |
> > cat profile.bashrc |
| 4 |
> > if [ "${HOSTNAME}" == "gentoo64.infinera.com" ]; then |
| 5 |
> > # This does not work, why? |
| 6 |
> > [ -z "$_once" ] && EMERGE_DEFAULT_OPTS="${EMERGE_DEFAULT_OPTS} -k n" && _once=1 |
| 7 |
> > [ -z "$_fonce" ] && FEATURES="${FEATURES} buildpkg" && _fonce=1 |
| 8 |
> > export EMERGE_DEFAULT_OPTS |
| 9 |
> > export FEATURES |
| 10 |
> > fi |
| 11 |
> > |
| 12 |
> > If I add logging inside I see that these are set but emerge |
| 13 |
> > does not build binpkgs, what am I missing ? |
| 14 |
> > |
| 15 |
> > sys-apps/portage-2.3.79 |
| 16 |
> > |
| 17 |
> > Jocke |
| 18 |
> > |
| 19 |
> |
| 20 |
> You can use /etc/portage/package.env to modify FEATURES. The bashrc is |
| 21 |
> evaluated only when executing ebuilds, so it's not appropriate for |
| 22 |
> FEATURES modifications. |
| 23 |
|
| 24 |
I did try adding --buildpkg to EMERGE_DEFAULT_OPTS too, same result
|
| 25 |
I do need to do this in the profile and last I tried package.env it didn't work
|
| 26 |
in profiles, has that changed?
|
| 27 |
|
| 28 |
In general I think /etc/portage is just another profile so things like
|
| 29 |
package.env should also work in a regular profile.
|
| 30 |
While at package.env, the other day I wanted do in package.env:
|
| 31 |
if not "cat/pkg" do my_extra.conf but I could not find
|
| 32 |
a NOT syntax for package.env, is there one?
|
| 33 |
|
| 34 |
Jocke |
Archives