From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060202 Fedora/1.5.0.1-2 Firefox/1.5.0.1 Description of problem: I think it would be more useful if pirut didn't automatically quit after hitting the completing a transaction. I don't know if this is eventually planned for or not. In using it today, adding and removing a few packages in one transaction caused some dep problems. I then tried proceeding in smaller chunks but having to restart pirut after each step was less than optimal. I realize broken deps may be less of a problem when we're not dealing with rawhide, but I don't really see a reason to force a user to build one big transaction instead of being able to do it in smaller pieces. Version-Release number of selected component (if applicable): pirut-0.9.8-1 How reproducible: Always Steps to Reproduce: 1. install something with pirut 2. 3. Actual Results: After installing, it quits. Expected Results: It should stay running in case I want to install or remove something else. Additional info:
The problem is that by doing installs, it basically invalidates the set of information we have and we'd have to do a lot of rechecking.