you're right, the --with-db=no seems to produce a lot of errors.

but, how can i prevent people from building db based systems?

if they can, they will do and if it fails, nobody will ask, but will  
say, that rpm5 has a bug on qnx.
i don't like those lines. so, i'd like to get a solution, which

   - either is worlig with db support
   - or preventing from using it, as much as possible

will the below mentioned change set any default to sqlite3?
can anyone switch back to berkeley db from the command line?
what about an existing berkeley db database and the rpm5 version?

-piet


Am 27.01.2008 um 20:26 schrieb Jeff Johnson:

>
> On Jan 27, 2008, at 2:19 PM, Peter Kalbus wrote:
>
>> i totally agree, that berkely db support on qnx is not an issuues  
>> for rpm5 itself.
>>
>> additionally i like to ha a clean qnx support with db support.
>>
>> as this is currently a problematic point and the suggestion is to  
>> use sqlite on qnx, i try to get it compiled with the following  
>> options to configure:
>>
>>   --with-db=no --with-sqlite=yes
>>
>> if this is a working configuration, that's fine. as berkeley will  
>> release db 4.7, which should have qnx support, the --with-db can be  
>> moitted again.
>>
>> what about this solution?
>>
>
> Probably easier is compiling rpm with both Berkeley DB and sqlite3,
> rpm uses certain Berkeley DB defines and structure names, and its  
> easier to just
> use what is in db.h than it is to figger out what defines/structs  
> are needed
> and where/why/how to supply an alternative definition.
>
> But there are a few people who have managed to compile rpm without
> Berkeley DB and db.h.
>
> Then all that needs changing is these two macros (3==bdb, 4=sqlite3)
>
> %_dbapi 3
> %_dbapi_rebuild 3
>
> 73 de Jeff
>
> ______________________________________________________________________
> RPM Package Manager                                    http://rpm5.org
> Developer Communication List                        rpm-devel@rpm5.org