Re: RE: rpmUtils cvs repository

Paul Nasrat <pauln-xGvoirzvwgBWk0Htik3J/[email protected]> Tue, 23 Mar 2004 08:35:49 +0000
Newsgroups gmane.linux.redhat.rpm.python
Message-ID <[email protected]>
On Mon, Mar 22, 2004 at 12:18:51PM -0500, Adam T. Gautier wrote:

> My only comment 
> on SV's rpmUtils is that it seems to just be a collection of functions.  
> I would like to see (and incidently is the approach that I am taking) a 
> more OO approach.  

Cool - it'd be great if you could discuss your thoughts here.  I'm aware that
currently rpm-python maps closely onto rpmlib rather than what people might
expect.  On the other hand rpm-python's use means that I still need to preserve
that atm.  Making it easy to layer is being done atm.

Also taking all three approaches (rpmlib, functions, objects) means we have
room for discussion.

>This is just after a quick glance of SV's rpmUtils 
> and I plan to dive into that code more.   I think the most important 
> thing after an easy to user rpm-utility module would be to have simple 
> example code for Add, Delete, Signature and Searching of the RPM 
> database.  

Documentation (docstr and examples) is known issue.  Some of that exists in
doxygen but I guess that may not be the expected place.  Duplicating \class in
the class level docstrings is something I've wondered about - particularly if I
can do via pre-processing.  The other side is getting this stuff into max-rpm
too.

> Also, what would it take to get ANY rpm-utility module added 
> to the rpm-python*.rpm used by distros?

My roadmap is to provide more in python than done presently.   This list and
discussions here with code and patches will definitely get considered.  

As well as go through what is there and missing from python->rpmlib.  My stuff
will go into HEAD, sane stuff into rpm 4.3 - but I have no control on that, but
if it's sane it should happen.  What other distros take is up to them, but I'd
like to think they'd move with the times.  

Paul