A way to ensure rpm database robustness?

[Reshetova, Elena]

Hi,

 

I have a simple question and sorry if it was asked before and I just didn't
find it in archives.  

Suppose we run rpm operation (installation, update or anything) on an
embedded device and power suddenly goes off. This can happen if user removes
the battery for example. 

In such cases, rpm database can get corrupted since the operation was
stopped in the middle. Rpm database can be rebuild after, but this is quite
annoying to do. Is there any ways to ensure that database stays sane even in
such cases? Of course some wrapper can be used for rpm to do the checks,
backup database and etc., but does rpm itself have anything for it? 

 

Best Regards,
Elena. 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-list/attachments/20130103/701053b7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7220 bytes
Desc: not available
URL: <http://lists.rpm.org/pipermail/rpm-list/attachments/20130103/701053b7/attachment.p7s>