Skip to content
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

Better naming of the cache directory #112

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mikhailnov
Copy link
Contributor

This is microdnf, not yum.
Normal dnf uses /var/cache/dnf. It is not a good idea to reuse it.
But there is no need to use /var/cache/yum, at least in ROSA where this package did not exist before.

Naming cache directory as "microdnf" allows to own it properly in the RPM package.

[ this pull request is a suggestion, I am not sure that you will want to change location on the fly, breaking compatibility ]

This is microdnf, not yum.
Normal dnf uses /var/cache/dnf. It is not a good idea to reuse it.
But there is no need to use /var/cache/yum, at least in ROSA where this package
did not exist before.

Naming cache directory as "microdnf" allows to own it properly in the RPM package.
@Conan-Kudo
Copy link
Member

I'm not sure we wouldn't want to use the /var/cache/dnf directory. @kontura, what do you think?

@Conan-Kudo Conan-Kudo requested a review from kontura June 13, 2021 22:56
@mikhailnov
Copy link
Contributor Author

Are any locks made to prevent parallel usage of it by dnf and microdnf?

Copy link
Contributor

@kontura kontura left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are locks but I think microdnf doesn't use the same code as dnf for caching. Even the contents of /var/cache/yum and /var/cache/dnf look different so I don't think we can easily share the cache.

Because of that I feel we shouldn't mix both types of cache in the same directory.

Maybe we could leave such a change for dnf5?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants