On Wed, Apr 17, 2013 at 05:17:42PM +0300, Panu Matilainen wrote: > Time for a status report, just to let you know I haven't forgotten or > abandoned this "project".
That's good to hear ;-) > All direct BDB ties in rpmdb.c were cut out last month, been pondering > about the backend API since then. Since that "work" was just going around > in circles I figured the more practical approach of trying to ram the > newrpmdb code into rpm might help get things going again. > > After a bit of poking around in the last two days, I have bits and pieces > in semi-working state. However what soon became very clear is that while > BDB might be technically gone from rpmdb.c, its spirit remains there rather > strongly (not that this is particularly surprising) Yes, the newrpmdb code doesn't have a "cursor" in the BDB sense. I did that on purpose, because I wanted to make clear that operation results don't have a state, i.e. I don't have to define any semantics when there's a cursor still open and the database gets changed. It should be easy though to either hide the cursors in the BDB code or implement a dummy newrpmdb cursor. Cheers, Michael. -- Michael Schroeder m...@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} _______________________________________________ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint