-
Notifications
You must be signed in to change notification settings - Fork 401
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
Change the behavior of history
when nothing is changed by group install
#2096
Labels
Comments
Thanks for the report, the issue is valid. To fix this, I think the behavior of group install would need to change, so that it produces an empty transaction if there is nothing to do. Interestingly, it is already so for group remove, so maybe it would be possible to implement it also for group install. The behavior is the same for dnf5, so it should be fixed there as well - rpm-software-management/dnf5#1492 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When nothing changes in the result by
group install
, I would suggest changing the behavior of thehistory
so that nothing appears for that event.But since it is about QoL, it should be a low priority.
The version of
dnf
used is as follows.When some packages are installed by
group install
, the history will look like this.Then, when the same is done again, the
history
is updated as follows, even though no updates, new installations, or other things have happened.I would suggest, for example, that the behavior of the
history
withgroup install
be changed to the same asinstall
withoutgroup
, as shown below.However, the current
history
behavior described here may be reasonable in ways I have not thought of.If so, I would appreciate a few hints on that point.
The text was updated successfully, but these errors were encountered: