command line EMERGE_DEFAULT_OPTS partial cancelling? [work@]

[CaptainBlood]

EMERGE_DEFAULT_OPTS="... --tree ..." in /etc/portage/make.conf here.

wiki

I feel quite dumb asking :
How to suspend the feature from command line when calling emerge?

Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

[grknight]

Example.. emerge --tree=n Every emerge option, because it is parsed by python, can have --option=value to set or enable/disable anything.

[CaptainBlood]

Nice, Couldn't get it from

[CaptainBlood]

Oops here:

[grknight]

Looks like this is one exception to the rule. Most of the options can do this, but not tree for some reason. Certain options make sense not to be able to be reversible for the mode (like --sync).

Maybe this could be a feature request where it makes sense.

[CaptainBlood]

Current one liner of a workaround:

[CaptainBlood]

[szatox]

I see you came up with a very creative way to override config with env.
At this point, wouldn't it be easier to make default opts environmental variable an empty string and just provide the switches you want manually instead of running emerge twice and mangling the output with an almost unreadable regexp?

I wonder, why do you NEED to unset --tree? I know it changes output format, but I don't think it's supposed to change the result of requested operation in any way. Do I miss something?
_________________
Make Computing Fun Again

[CaptainBlood]

[Hu]

You can use --ignore-default-opts to disable all the defaults. However, if you have some defaults that you want and some you do not (which is how I interpret the original question), then this disables too much.