Re: dnf history - change in how rpmdb checksum is computed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



What's the benefit in changing to be compatible with YUM as opposed
to stickin with current alogorithm ?
If a user migrates from RHEL 7 to the next version of RHEL (or CentOS),
there will be continuity in used algorithm and history db checksums.
It's important to some enterprise customers to keep the history db in a good shape.
Fedora users don't care about that much in general.


Surely if we don't change it, even fewer users will notice that DNF's
behaviour is different from YUM's, since DNF has been the default for
many releases now.

I could understand the motiviation to stay compatible with YUM if we
were only just about to switch Fedora from YUM to DNF, but time is
way in the past now. Shouldn't we optimize for the fact that DNF is
the more widely deployed & used tool, and thus not worry about
YUM compatibility in respect of the history DB ?
Unfortunately RHEL knows nothing about DNF yet
and it's YUM compatibility what matters.

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/JYCKOFC223P5RADHMZOBNBA5L2V6EGYS/

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux