Re: [gentoo-dev] Strip features via profile.bashrc

[William L. Thomson Jr.]

On Sun, 19 Nov 2017 22:27:26 -0500
Mike Gilbert  wrote:
>
> FEATURES gets processed by portage too early for bashrc settings to
> have any effect.

Glad to have that confirmed, as that is what I experienced.
Feel like I was in this commercial...
https://www.ispot.tv/ad/wlDi/directv-head-bang
 
> I do not think there is any equivalent to /etc/portage/package.env
> that can be defined in profiles.

Great thanks for confirming!

> I do not see any existing bug asking for this enhancement, so you
> could probably file a new one.

Will do, though I haven't had much luck in my profiles features
request. Sets went no where quick... Maybe this will have better luck!
https://bugs.gentoo.org/638196

-- 
William L. Thomson Jr.

Re: [gentoo-dev] Strip features via profile.bashrc

[Mike Gilbert]

On Sun, Nov 19, 2017 at 9:57 PM, William L. Thomson Jr.
 wrote:
> I am trying to replicate like /etc/portage/package.env type function.
> For some packages I had FEATURES="-buildpkg". I cannot seem to
> replicate this what so ever with profile.bashrc.
>
> Not sure how via a profile in an overlay/tree, not /etc/portage, one
> can add/remove features. I do not seem to have this problem with other
> stuff. I_KNOW_WHAT_I_AM_DOING works for skipping pre-merge checks.
> I am also able to add CFLAGS/CXXFLAGS. Which I noticed were being added
> like 4 times, so I added in a phase check/hook.
>
> https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/profiles/linux/amd64/profile.bashrc
>
> For some reason I cannot seem to add or remove FEATURES. I can see them
> in the shell. But they seem to have no effect. At least with regard to
> buildpkg FEATURE.
>
> phase: setup features: assume-digests binpkg-logs buildpkg ...
> phase: setup features: assume-digests binpkg-logs buildpkg ...
>
> In this case its removed, but still makes a binpkg.
>
> phase: package features: assume-digests binpkg-logs
> config-protect-if-modified ...
>
> .Doesn't show but in my output there is a gap, 2 spaces
> where it was. I can see the profile.bash being processed and doing its
> thing.
>
> I have tried export and set, neither have effect. Even when replaced
> with -buildpkg. Seems like make.conf is sourced or something for that.
> I do not think I am setting it to late. I cannot seem to set it for the
> build env.
>
> Any way to do this? A bug?

FEATURES gets processed by portage too early for bashrc settings to
have any effect.

I do not think there is any equivalent to /etc/portage/package.env
that can be defined in profiles.

I do not see any existing bug asking for this enhancement, so you
could probably file a new one.