Re: [SUMMARY] error with rpm 4.0.3 libs

[Jeff Johnson <jbj JBJ ORG>]

On Thu, Dec 27, 2001 at 04:37:08PM -0300, André Ladeira wrote:
> Hi,
> 
> First, thanks to jeff johnson, that posted my only answer. Thanks jeff!
> 
> The only problem with your idea of statically link the rpm libs is that the
> final exucutable grows to 5Mb! But you are right, it's insanity trying to do
> something
> sophisticated with these libs....
> 

You're gonna end up with bloat independent of static/dynamic linking.

> But I found by myself  a weird solution: I wrote a shared library  that when
> called
> with dlopen just link at run time to itself all the libraries of rpm and
> then I can use dlopen on my own lib for indirectly access the functions of
> rpm API. This lib have only 3kb and my executable remains low sized.
> 
> what is the use of this? I will try to explain....I'm writting an
> application that need to read data from rpm database, no matter the version
> of rpm. My initial idea is to ask  rpm about its version and then load the
> right libraries with dlopen and  the right functions with dlsym (I know in
> advance the
> right ones for each version..). But this scheme failed with rpm 4.0.3
> because of the
> cross reference from one lib to another as I mentioned before.
> 
> ( Jeff, now you know why I need rpm 4.0.1, 4.0.2 .... :-)  )

You're still insane :-)

And you're mistaken if you think that there's any change in the
database, or the rpmdb iterator's necessary to access the database,
in any of the rpm-4.0.x versions. Yes the rpmdb iterators moved to
librpmdb, but the API is the same.

73 de Jeff

-- 
Jeff Johnson	ARS N3NPQ
jbj@jbj.org	(jbj@redhat.com)
Chapel Hill, NC