On Feb 9, 2011, at 9:30 AM, Matthew Dawkins wrote: > > > So what I have seen is that if you are trying to bootstrap coming from < > rpm-5.3.x system, db51-utils needs to be present for dbconvert.sh to work. > If not, no problems what so ever were encountered. >
Yes. You will _NOT_ be able to do the conversion or fix any problem
with an rpmdb using db51_recover.
You need the executable installed in order to invoke. This should
surprise noone.
All that is surprising is that with "RPM ACID" you MUST be prepared
to install additional packages like (in Cooker) the db51_recover package.
> IMHO, I think adding that requires, for the simple sake of covering people
> during the possible upgrade, covers the cost of the 98Kb in size of the pkg.
>
For Mandriva Cooker systems yes, a Requires: makes perfect sense.
But for --with-db={external,internal} "Have it your own way!" RPM distribution,
then its less clear whether RPM needs the Requires: or not.
In fact, RPM was distributed with Berkeley DB internal and internal
db_recover exactly to avoid the failure case of not being able to
repair an rpmdb issue.
But that is _NOT_ what all distros choose to do building RPM. All
distros I know of are asking
How do I build RPM with Berkeley DB external?
ignoring the fact that there's no one single version of Berkeley DB.
And around adn around it goes. What has not changed at all is this
RPM without Berkeley DB (and tools) is useless.
73 de Jeff
smime.p7s
Description: S/MIME cryptographic signature
