The idea is that it prevents the kind of scenario described in the commit
message from happening in the future. If an unknown database is configured, rpm
cannot know if its just a typo or some new backend from a newer rpm version
(consider eg various chroot scenarios), and together with the implicit database
init (which is really the evil thing here) it's downright dangerous. It's not
the most common scenario for sure, but this chain of events managed to nuke the
rpmdb on my own laptop...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/commit/471b7be4bd5cc7f245f9aa00c7784a7056e439b7#commitcomment-44295216
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
