Mark Hatle wrote:
> Bernhard Rosenkraenzer wrote:

>> The first thing coming to mind is the rpm database format -- we've 
>> been using
>> db4 so far, has anyone compared db4 and sqlite to see if switching to 
>> sqlite
>> has any benefits/drawbacks (speed, db file size, ...)?

> We use sqlite, but my recommendation is unless there is a very specific
> reason to use sqlite, don't.

> (sqlite is also considerbly slower then db4, due to the emulation
> aspects..  it also takes more space.. etc..)

MacPorts uses SQLite for RPM 4.4 (since 2005), I forgot what the
reason was but I think it was licensing rather than technical...
Before jbj's RPM 4.4.2 it was using RPM 4.0.4, so *lots* changed.
(it builds with both backends, just sets dbapi to "4" by default)

Most likely it will stick with sqlite API for current RPM 4.4.9,
but that could of course be re-evaluated before the 4.5 upgrade.
But my "%universal" Mac RPM5 release, it's probably going to use
default/internal db4 - unless there's a good reason to do sqlite3 ?

See also http://rpm5.org/community/rpm-devel/0395.html "migrating"
(assuming RPM5 with support for both of Berkeley-DB and SQLite...)

--anders