scripts not using --ask should be broken, and should be rewritten to query portage and then specifically use --dontask, --justdoit, --dosomethingunexpected or some other option name that makes it obvious that you are going ahead with possibly unintended consequences... as for end users, portage should be "safe by default" it is very easy to hose a system by accident and only takes a moments slip in concentration to forget to add --ask (which I do even if I've queried portage beforehand using other methods...)
No, interactive by default is bad. Users should be more careful. (And if you add --ask by default you only train them to hit the enter key without looking) If you want to have this by default add it to EMERGE_DEFAULT_OPTS in make.conf and enjoy :)
consider adding this to stage3 youre getting more and more Debian (ie new to portage users) now its thrashing itself to death
Changes to the default user interface make people angry.
I like this idea. But usually when I change a default, I get a lot of shit for it. This especially holds for making stuff interactive. The last time I added interactivity, I had to remove it because of all the shit I got. And that was not 1/100th as invasive as what you are suggesting (it merely added interactivity to an already interactive session). So, I'm sorry to say that this will never happen. One thing that might be plausible is to have some meta-variable "safe-defaults" or "interactive" that can be set in make.conf (e.g. in EMERGE_DEFAULT_OPTS), that turns on 'ask' and whatever else it makes sense for it to turn on. The handbook could then suggest that inexperienced users turn this on when setting up make.conf.
Specially as the safest option portage have is not --ask but --build-pkg, no matter if the user answer blindly or not, the package will be done and that's the safest way to put a user out of trouble.
--depclean & --unmerge don't build packages, but do allow for --ask
if you default enable --build-pkg it doesn't matter if user is even doing depclean or unmerge on his toolchain. while --ask for depclean won't stop anyone from hitting the yes key blindly.
(In reply to nobody from comment #7) > while --ask for depclean won't stop anyone from hitting the yes key blindly. Maybe the --ask-enter-invalid option helps.
