Re: RE: rpmUtils cvs repository

> Done, I think the rpm-python should be very closely mapped to rpmlib(And 
> probably stay that way), That gets rpmlib into python and then 
> abstraction(s) from that can be made rpm-objects or what ever.  I 
> actually like the complexity that is currently there becasue the RPM 
> system is somewhat complex and should anyone what do anythin directly 
> the need to seriously look into the C code and rpmlib itself.  I don't 
> thaink that should change.
Are you suggesting that all the ts object abstraction that rpm-python
currently does should be dumped and it should just be little more than a
swig library?

I'm pretty sure I don't like the 'everything revolves around a ts,
sorta' framework that is currently in place but I don't think we want to
draw directly from the c libs as a solution right away.


> I need to build for another project higher level concepts and need 
> things that are well documented inside of python an are virtually safe 
> from my mucking around (I don't want to corrupt my rpmdb).  the current 
> mapping with a good abstraction should provide that for me.

if you can't corrupt your rpmdb then you can't install packages, either
:)

-sv