-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.0 breaking change] - Don't generate sqlite metadata by default #338
Comments
I also support to change the default to not generate yum database as default. Note - such a change cannot be back-ported to RHEL. |
Suggestion - given the changes proposed for "1.0" in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/25J55FCQKTMCEOBS7EZCTP34RKLUOUQ3/, I propose we go a tiny bit further.
Pulp currently does use |
@kontura The original proposal here is finished, should we close this and file new issues for dropping --no-database? |
That sounds good. 👍 |
yum supports XML metadata even though it prefers sqlite, but DNF doesn't use sqlite metadata at all. Since generating and compressing the sqlite metadata is very expensive and removing it should not break compatibility with RHEL, and also provides no benefit nowadays, it might be reasonable to disable it by default, or even compile the feature out by default on most platforms.
The only two non-yum users I am aware of are: mdapi, and repoview. repoview is defunct, and the fedora infra looks like it specifically adds --database or --no-database as needed so the default shouldn't affect it, which means mdapi shouldn't be broken by a change in default.
It would probably be good to update that eventually, though.
The text was updated successfully, but these errors were encountered: