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?

-piet


Am 27.01.2008 um 19:26 schrieb Jeff Johnson:

>
> On Jan 27, 2008, at 1:14 PM, Peter Kalbus wrote:
>
>> the qnx support is not yet ready. there are two open points:
>>
>>  - fts.c is not compiling (needed code is included, but #ifdef not  
>> yet ready)
>
> I will either change the #if def to __QNXTO__ or you will send the  
> patch
> for configure.ac before 5.0.1 gets released.
>
>>  - db 4.6.21 support DB_PRIVATE not yet finalised
>>
>
> I can't support DB_PRIVATE in rpm. It's a Berkeley DB issue, and
> the flaw appears to be with QNX mmap(2) support. That's
> outside the realm of what's possible rpm-5.0.1 (or in rpm itself).
>
> databases need locks, DB_PRIVATE disables locks. And rpm already
> has means to configure a per-process shared/exclusive fcntl lock.
>
> I can/will tell you what patches/configuration are needed to use  
> DB_PRIVATE
> on QNX.
>
> And I recommend looking at sqlite3 for "production" rpm use on QNX.
>
>
>> let me know, what the schedule for 5.0.1 is, so i can see, if qnx  
>> support is still possible
>>
>
> Schedule is being devised as we speak.
>
>> but, i guess, that qnx support is not really a blocking issue ;-)
>>
>
> Not blocking, but it would be nice to have QNX be drop-in to the  
> greatest
> extent possible in rpm-5.0.1.
>
> 73 de Jeff
> ______________________________________________________________________
> RPM Package Manager                                    http://rpm5.org
> Developer Communication List                        rpm-devel@rpm5.org