emerge --ask does a nice job at asking if you want to emerge an entire list of packages, but some sort of (advanced) feature that enabled a user to accept or deny a particular merge would be quite nice. Example: During "emerge --prune", a list of slotted packages will be shown, and all those packages will be unmerged or not. So the user uses "emerge --prune --confirm" or something like that, and portage will ask about each package to be unmerged, one at a time, before any merges happen. Then, before any changes are made, portage would re-list the packages to be removed, with a final "Yes/No". Yes would result in the changes being committed, and No would exit.
(In reply to comment #0) > --confirm" or something like that, and portage will ask about each package to > be unmerged, one at a time, before any merges happen. Then, before any changes > are made, portage would re-list the packages to be removed, with a final > "Yes/No". Yes would result in the changes being committed, and No would exit. From my perspective, that would be quite annoying for anything more that just a few packages. I'd say a curses or X based gui would be better suited (more scalable) for such purposes.
(In reply to comment #1) > (In reply to comment #0) > > --confirm" or something like that, and portage will ask about each package to > > be unmerged, one at a time, before any merges happen. Then, before any changes > > are made, portage would re-list the packages to be removed, with a final > > "Yes/No". Yes would result in the changes being committed, and No would exit. > > From my perspective, that would be quite annoying for anything more that just a > few packages. I'd say a curses or X based gui would be better suited (more > scalable) for such purposes. > Good point, an ncurses interface would be very nice. Wonder if there's any chance of that coming about instead of this. Now I want to edit my suggestion to be something with ncurses.
*** Bug 61889 has been marked as a duplicate of this bug. ***
*** Bug 202410 has been marked as a duplicate of this bug. ***