I've been avoiding backporting rpmiotypes.h to the
5.1.x branch since last August.

Increasingly, I'm wasting too much time rearranging "stuff"
to have two parallel (but divergent) implementations within RPM,
code.

There's not a whole lot going on in <rpmiotypes.h>. Its
basically designed as The One Place that typedef's are defined.

What I need very soon in rpm-5.1.x however, is the rpmiob abstraction.

The rpmiob type is currently an allocation container
to keep track of an address, the current size,
and the allocated size of a buffer. I want to
add posix mutexes and gather rpmiob types into
an allocation pool.

I will likely strip out everything but typedef's and
rpmiob methods from my first pass at backporting rpmiotypes.h
to 5.1.x.

But I gotta start somewhere, two parallel (but divergent)
implementations is increasingly getting in my way.

Opinions?

73 de Jeff


______________________________________________________________________
RPM Package Manager                                    http://rpm5.org
Developer Communication List                        [email protected]

Reply via email to