Red Hat Bugzilla – Bug 459710
Pulls in 9 megs of compat packages
Last modified: 2013-07-02 19:31:14 EDT
rpm now pulls in 9 megs of compat-db packages, thus requiring a corresponding trimming of that much in applications to keep things like the livecd fitting.
Either rpm needs to link to the main system db version, rpm needs to carry its own version, or we need to revisit how the compat-db package is done so that we can not have such extreme bloat.
Sticking on F10Blocker, although preferably we can get this resolved pre-beta
Sadly it doesn't even look like it got looked at pre-beta.
Added review requests for every BDB present in compat-db. The requests are to introduce compat-dbs for each version of old BDB to avoid dep bloat.
We can drop compat-db after compat-db43, compat-db45 and compat-db46 are reviewed and included.
Current compat-db dependencies are these:
$ repoquery --whatrequires libdb-4.3.so
$ repoquery --whatrequires 'libdb-4.3.so()(64bit)'
$ repoquery --whatrequires libdb-4.5.so
$ repoquery --whatrequires 'libdb-4.5.so()(64bit)'
$ repoquery --whatrequires libdb-4.6.so
$ repoquery --whatrequires 'libdb-4.6.so()(64bit)'
We *can* move rpm to BDB 4.6. It's just that then there will be no more easy way back to 4.4.2.x (see https://fedoraproject.org/wiki/Features/RPM4.6#Contingency_Plan). If we consider we're past the point of no return anyway (I'd tend to think so but...) then ok by me.
The wiki page 'documentation' points to a completely empty:
I finally decided to add compat-db45 and compat-db46 subpackages to compat-db in a way that compat-db is just a dummy package containing nothing except requires to compat-db45 and compat-db46. The old db4.3 can be dropped now since nothing depends on it after all.
The dependent packages that contain Reqiures: compat-db won't break and those containing dependency on one of the legacy db4 libs will pull in just either compat-db45 or compat-db46.
Typically, in case of LiveCD just compat-db45 should be pulled in because of rpm, which is about ~2.7M in total.
Please let me know if you think it would break something. It should just work(TM) as the new compat-dbxx packages obsoletes old compat-db so the upgrade path should be kept.
compat-db is now split. RPM is now updated to live hopefully fine with the new compat-db.