On Tue, 2010-08-24 at 16:43 +0200, Radek Vykydal wrote: > >> > >> 1) have repos A and B enabled > >> 2) default packages for repos/installclass are added > >> 3) user adds/removes packages > >> 4) transaction is created > >> 5) (e.g.) user learns about some conflicts > >> 6) goes back in UI (to 1)) > >> 6) disables repo B in UI -> it is removed > >> 7) before going forward to 2), transaction needs to be reset > >> with the patched function > >> > > > > self.ayum.closeRpmDB() > > self.ayum._repos.close() > > self.ayum.comps = None > > > > or: > > > > self.ayum.close() > > > > > > These don't do what we need - to keep > ayum.repos (and their sacks) that had been set up > before 1) and modified in 6), and start only group/package > selection from scratch - which requires resetting > ayum.tsInfo if I get it right. > > What you are suggesting seems to me as starting > with a new YumBase object - that is going far too back > for us. It's not significantly farther. If you've already setup those repos then you'll only be adding them in and they'll be current and in the local disk cache. > Perhaps yum interface just is not suitable for doing things > like those in 1) - 7)? The set of pkgs available is intertwined with the groups available and how they are displayed, it's wrapped up together purposefully so I'm not sure how you extricate one from the other. -sv _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
