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

automatic: Consider reading the dnf4 configuration file for backward compatibility #1624

Closed
jan-kolarik opened this issue Aug 13, 2024 · 2 comments · Fixed by #1690
Closed
Assignees
Milestone

Comments

@jan-kolarik
Copy link
Member

The configuration for the automatic functionality has been moved to a different location compared to dnf4, as this functionality is now provided as a plugin (see the changes docs and automatic command docs). The content is backwards compatible, and since we are already reading multiple configuration file locations, we might consider applying the values from the original location for users who have migrated to dnf5.

@jan-kolarik jan-kolarik changed the title automatic: Consider reading the dnf4 configuration file for backwards compatibility automatic: Consider reading the dnf4 configuration file for backward compatibility Aug 13, 2024
@jan-kolarik jan-kolarik added this to the Fedora 41 milestone Aug 13, 2024
@keszybz
Copy link

keszybz commented Aug 13, 2024

I don't think the new location makes much sense. As a user, I really don't want to care or think about the fact this functionality is provided by a plugin. I'd vote for just using the old location (which is backwards compatible and makes the most sense for the user).

@jan-kolarik
Copy link
Member Author

I don't think the new location makes much sense. As a user, I really don't want to care or think about the fact this functionality is provided by a plugin. I'd vote for just using the old location (which is backwards compatible and makes the most sense for the user).

Yeah, good point, thanks for the feedback! If the plugin still needs to access the configuration at the standard plugin location, we can just add a symlink there.

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

Successfully merging a pull request may close this issue.

3 participants