Re: Proposal For rpm-objects module

>  I was also going to create a project around 
> this on sourceforge or something.  No offense to Duke(I went to Harvard 
> so down my nose I look) but would I be able to get access to the CVS 
> repository to continue my development? 

ok so:
 1. sourceforge sucks, let's not have an cvs repository we can't get to
with any reliability. :)
 2. my girlfriend graduated from harvard and she said you've got no room
to look down your nose at other institutions. :)
 3. access to the cvs repo is doable but the current layout gets tricky
for handing out access to people I don't know.. fun huh?


>  This is needed because I am 
> developing this within the scope of a bigger open-source project called 
> tiny-linux(a bit off topic, so I will not talk about here unless asked)  
> which requires the rpm objects and a rewrite/feature add of yum.


I'd like to know more about the features you want to work on in yum -
but yum-devel list might be a better place for that. They may be
features that are already in progress/on the table.

I think the structures look fairly good - I think you might get some
benefit by going through yum, up2date, system-config-packages and
anaconda and seeing how each handles the rpm objects - a little bit of
experience in those would help you to not make the same mistakes.

you should also be wary of how often you end up with open transaction
sets to talk to the rpmdb, some of those actions can get expensive.

Finally, look at how the TransactionWrapper class that Adrian wrote and
I thefted from up2date works. It might be a useful base to work from for
the rpmdb class. Especially wrt VSFlags.


-sv