RPM Community Forums

Mailing List Message of <rpm-users>

Re: Database compatibility with older versions?

From: Jeff Johnson <n3npq@mac.com>
Date: Tue 11 Mar 2008 - 16:11:10 CET
Message-Id: <E1C195E7-CFCA-4271-BB5E-9D177340F788@mac.com>

On Mar 11, 2008, at 10:50 AM, Martin Nicolay wrote:

> 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!
>

There are 2 issues being addressed by notes in INSTALL:

1) Stale lock detection (and automagic database repair) depend on
features that are present in db-4.4.x (+patches) or later. Hence the
"Version Minimum 4.5". But one can revert the stale locking handling
"feature" as well.

2) Support for linking "external" Berkeley DB is perhaps the most time
consuming rpm support question. Building Berkeley DB is non-trivaial,
and verifying that rpm built with all possible "external" Berkeley DB's
is functional is even harder. Hence "Use ... bundled Berkeley-DB  
copy, please!"

(aside) The "... modified ..." is a patch to use robust mutexes on  
linux kernel's.
You can easily live without "robust mutexes" and use Berkeley DB as  
distributed.

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

Use --with-db=external. The --with-dbapi={3,4} option is for selecting
bdb or sqlite when rpm is built with both.

> 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.
>

So customer "compatibility" forces vendor rpm to be used. Not suprising.

73 de Jeff
Received on Tue Mar 11 16:11:30 2008
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.