Actual results: After installing packages or removing packages through the search interface, pirut closes immediately. Expected results: It shouldnt do that
This is by design. The entire backend is very much transactional and moving away from that requires some substantial changes.
Can I have this as a enhancement request then?. I am not worried about the internal design. I would like to install more than one package at a time without having to reopen pirut everytime.
Why are you selecting one at a time instead of selecting a bunch at a time. Changing this is something we can look at in the FC6 timeframe, but I'm not 100% sure how realistic it really is.
I search for different things like lets say java and python and then install the interesting packages one at a time. Lazy cherry picking basically
*** Bug 183975 has been marked as a duplicate of this bug. ***
I agree that the current behaviour is not very convenient.
<AOL>"me too"</AOL> The problem with the current behavior - do one transaction, then exit - is that IMO usage of a graphical package tool is iterative by nature. That's especially true with the current default screen being broken into different major categories -- the usage inclination from the current UI seems to me to be going into one category, select what you want, apply, then move on to the next category To me, if I know what packages / groups I want and I just want to start an install and go, I'd use yum. If I'm bothering to get in the gui, I want something where I can explore, add stuff one at a time, read the info on each one, etc. There's also the practical reason - dependency conflict stuff doesn't display enough information currently to sanely figure out what's going on, so basically your only hope is to do multiple smaller transactions
Me Too. Please fix this. It totally sucks since it takes about 5 minutes to load.
(In reply to comment #8) > Me Too. > > Please fix this. It totally sucks since it takes about 5 minutes to load. Please stop the me too's. It doesnt help anyone and just adds to bugzilla mails unnecessarily.
Okay, things will no longer exit but you are forced back to the browse view for now. While not the best answer, it at least improves things somewhat. Retaining a visible package list is a lot harder since to get the new state of the rpmdb, we have to reinitialize some bits of yum which then leaves us with weird references to no longer existing things. And it should reduce the hit for the restart time.