For people who want to do things like full emptytrees to upgrade USE flags/CFLAGS, I suggest a 'no user intervention' option to emerge. This would automatically skip any packages (and their reverse deps) which require user intervention to emerge. This would avoid the issue such as, starting an emptytree, going to bed, then waking up to find it 10 packages later waiting at an EULA prompt.
user intervention should never be required if a packages does, it's a bug, file a bug against the pacakge that does
What you're after is a combination of bug #17367 and another one which I can't seem to find at the moment. This functionality will be available in a month or two.
Several packages require acceptance of an EULA or have fetch restrictions and will stop a emerge -e world dead in it's tracks until the user intervenes.
Jstubbs: No, he isn't looking for a variable, just for a --dont-bother-me (well, better named) switch that will avoid packages that need me to do something for them.
Comment #4 is a perfect description of what I want, although the other bugs look interesting. But even if we did the other two RFEs, we'd still end up with the problem of 'F' packages stopping the process.
I realize that and already have that feature working with portage locally. I was saying that it'll be a month or two before it's available.
*** Bug 58914 has been marked as a duplicate of this bug. ***
Actually, even just a "bug me about problems BEFORE we start" option would be enough (at least for me). So if half way down there is a fetch restriction, it warns about this and tells you WHAT the fetch restriction is and gives you the option to resolve it before you even start. I hate doing an emerge -Du world just to have to come back to a screen waiting for me to continue after getting j2sdk docs or something.
Marking this as dupe of 17367 since this problem will be solved for the EULA issue once ACCEPT_LICENSE is implemented. We can't fix fetch restriction anyway (it's a feature, not a bug! ;)). For any other package, user interaction during the emerge is a bug specific to that ebuild and should be filed seperately. *** This bug has been marked as a duplicate of 17367 ***
Um, no, that isn't what this bug is requesting. Instead, it wants packages with fetch restrictions to be more verbose up front, meaning at the time when you run 'emerge -uD world', and yell about it then, or perhaps simply get on with it. This isn't a dup, really.
right, thanks for clarifying :)
(In reply to comment #10) > it wants packages with fetch restrictions to be more verbose up front, That does not match comment #0. Please, lets just address one feature per bug.
No, piping yes into stdin won't do either. Something needs to be done for fetch-restricted packages, too, and emerge just dies with those and not display a [yes/no] prompt.
(In reply to comment #13) > No, piping yes into stdin won't do either. > > Something needs to be done for fetch-restricted packages, too, and emerge just > dies with those and not display a [yes/no] prompt. > Only one feature request per bug please!
This will be covered by RESTRICT=unattended *** This bug has been marked as a duplicate of bug 151113 ***
