Currently, emerge behaves as follows:
(principia:~) # emerge -Dua world
* IMPORTANT: 1 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.
These are the packages that would be merged, in order:
Calculating dependencies /
Would you like to merge these packages? [Yes/No]
At this point, a wise user enters "no" and does eselect news read. However since --ask is in action, perhaps emerge could ask after the "IMPORTANT" message whether the user wants to read those pending news items (maybe even during dependency calculations) such that it is not necessary to abort and start emerge again.
I guess a simple "eselect news read" call would do, after which emerge would simply resume what it was doing.
There's this notion that emerge should not be interactive apart from the merge question. autounmasking is an exception. Personally I don't see a problem with your suggestion. It makes sense. You would not want to waste time calculating dependencies twice.
If I see no objections within a week or two, I'll go ahead and implement this.
Thanks for the idea.
Well, I'm not really sure about changing interactivity here. You can always do ^z or use another terminal to read the news. But it's just a matter of habit.
Created attachment 382716 [details, diff]
Fixes the bug
This is in git:
This is released in portage-2.2.14_rc1
I'd like to request having this feature optional. Either through FEATURES or --option. Otherwise it totally disturbs my workflow with portage which I have for years.
It's its own option in git now.
(In reply to Alexander Berntsen from comment #7)
> It's its own option in git now.
Looking at the changes:
That may be the only UserQuery that is not conditional on --ask (it's conditional on --read-news instead). Maybe it should be conditional on both?
Created attachment 387084 [details, diff]
emerge --read-news: prompt only if --ask
This patch makes --read-news have no effect unless --ask is enabled.
I don't care particularly much. Patch looks good to me. Go ahead and push it.
(In reply to Alexander Berntsen from comment #10)
> I don't care particularly much. Patch looks good to me. Go ahead and push it.
Thanks, it's in git now:
With typo fixed:
This is in the portage-2.2.15 release.