RPM Community Forums

Mailing List Message of <rpm-users>

Re: Database compatibility with older versions?

From: Martin Nicolay <m.nicolay@osm-gmbh.de>
Date: Tue 11 Mar 2008 - 15:50:54 CET
Message-ID: <Pine.LNX.4.63.0803111447380.7781@wsmn.osm-gmbh.de>
Thanks for Your detailed answer!

On Mon 10 Mar 2008, at 17:30:35 CET Jeff Johnson wrote:
> 2) Coexisting vendor <-> custom rpm.
>         rpm's database needs are rather modest, so it is quite feasible to
>         build ~5 versions of rpm-5.x, with the same version of Berkeley DB
>         used by the vendor's version of rpm.

I have no problem with many different rpm-packages with matching db-version
for our supported platforms, but in INSTALL is written:
	Berkeley-DB: Version Minimum 4.5
and
	Use modified bundled Berkeley-DB copy, please!

How do I use the vendors Berkeley-DB?
	--with-db=external
or
	--with-dbapi=<version-number>

We have no compatibility issue with Sun because all entries within the 
rpm-database are our own packages and will be managed with our own rpm 
binary.  Our problems are with rpm-databases which contains also system 
packages.  In future I would like to disentangle our packages into our own 
rpm-database but old installation at customers site require compatibility.

	Martin

-- 
_______________________________________________________________________________
No MS-Word attachments (http://www.gnu.org/philosophy/no-word-attachments.html)

OSM GmbH                               Mail    m.nicolay@osm-gmbh.de
- Softwareentwicklung -                Telefon +49-201/8955-5
Ruhrallee 191                          Fax     +49-201/8955-400
D-45136 Essen                          Web     http://www.osm-gmbh.de

Registergericht: Amtsgericht Essen, HRB 11281
Geschäftsführer: Johannes Kuhn, Christian Damsky, Axel Roland
_______________________________________________________________________________
Received on Tue Mar 11 15:50:58 2008
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.