On Tue, Dec 16, 2008, Eric MSP Veith wrote:
> for my build environment I want to create a basic distro that comes with
> only the minimal requirements. This works quite well, except for RPM 5
> whose dependencies I do not dare to touch.
> Two things disturb me: First the sqlite3 dependency and the need to have
> BerkeleyDB libraries around. The sqlite3 problem can be solved quite easily
> by just disabling it when running configure; however, the latter I don't
> understand: rpm5 brings it's own bdb, why does it rely on an external set
> of libraries?
RPM ships with Berkeley-DB because it slightly modified it and RPM
wants to make sure that it is always able to correctly build against
Berkeley-DB. Except in cross-platform/non-Linux situations, RPM should
work just fine also with the external Berkeley-DB as long as this
Berkeley-DB is of a recent enough version. In a cross-platform/non-Linux
situation I would be more careful with the external version.
> I assume that this comes from dynamic linking (?), and I guess that doing
> static linking would solve the problem. Is there an *elegant* way to link
> the supplied bdb distributions statically?
The supplied Berkeley-DB _IS_ linked statically into RPM AFAIK.
But perhaps I misunderstand your question...
Ralf S. Engelschall
Received on Tue Dec 16 16:47:46 2008