On Feb 7, 2008, at 12:07 PM, Peter Kalbus wrote:

>
>>
>> Added.
>>
>
> Thanks!
>

Well I spoke too soon. Almost added, the checkin is pending ...

>>
>> What is the data type in db.h on QNX? if "u_int32_t" is being used in
>> db.h,
>> then changing the cast is not the right fix in rpmdb.c.
>>
>
> Since QNX is currently not supported from db 4.6.21, there is no  
> build_qnx location with a db.h file avaiŽlable. But if that would  
> expect, I guess that it would contain "typedef unsigned int  
> u_int32_t;", which is similar to the other ones.
>

OK. I'd like to solve the issue the same way that Berkeley DB does.

The rpmdb (actually the internal dbiFoo()) API uses the Berkeley DB
DBT (and mebbe 4-5 other typedef's) and I'd like not to diverge
if at all possible. For the near term, rpm with Berkeley DB is
has 1st class support, there are no substitutes (sqlite lacks certain
functionality and also has feture changes that prevent me from saying
"1st class support" wrto sqlite3. Fixable sure, just not done).

73 de Jeff