Bug 153980 – emerge does not always honor --ignore-default-opts

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Justus Ranvier 2006-11-03 17:22:07 UTC]

I have --ask in my EMERGE_DEFAULT_OPTS. I've noticed that recent versions of portage will still behave as if --ask was used even if I specify --ignore-default-opts

boron /usr/src #emerge --ignore-default-opts --sync
Do you want to sync your Portage tree with the mirror at
rsync://64.127.121.98/gentoo-portage? [Yes/No]

My portage version is 2.1.2_rc1-r1

[Comment 1 Jakub Moc (RETIRED) 2006-11-03 17:30:24 UTC]

*** Bug 153981 has been marked as a duplicate of this bug. ***

[Comment 2 Zac Medico 2006-11-03 18:34:34 UTC]

Thanks, this is fixed in svn r4926.

[Comment 3 Justus Ranvier 2006-11-03 20:17:52 UTC]

On a related note: is there a command line switch that negates --ask, without requiring --ignore-default-opts?

It would be nice to do something like:

emerge -u --noask (--yes?) world

instead of

emerge -u --ignore-default-opts --(any other default options except for --ask) world

[Comment 4 Jakub Moc (RETIRED) 2006-11-04 00:22:34 UTC]

(In reply to comment #3)
> On a related note: is there a command line switch that negates --ask, without
> requiring --ignore-default-opts?

An example of featuritis? :P No, there's not and I don't see the point, we'd end up w/ tons of no* switches in the end.

[Comment 5 Zac Medico 2006-11-04 00:33:23 UTC]

(In reply to comment #4)
> An example of featuritis? :P No, there's not and I don't see the point, we'd
> end up w/ tons of no* switches in the end.

We already have tons of no* switches. Actually, I've recently added a --color < y | n > option and deprecated the --nocolor option.

I know that genone has been thinking about a framework that would give users the ability to define their own options.  If we implement something like that, then of course you should be able to do almost anything.

[Comment 6 Zac Medico 2006-11-05 23:40:40 UTC]

This has been released in 2.1.2_rc1-r4.