Am 17.04.24 um 16:44 schrieb Jonathan Wright:
On Wed, Apr 17, 2024 at 9:43 AM Leon Fauster via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>> wrote:Am 17.04.24 um 15:59 schrieb Jonathan Wright via devel: > Valley 7.2.5 stable was released yesterday. Builds are in Bodhi and > ready for testing/feedback. > > https://bodhi.fedoraproject.org/updates/?search=valkey-7.2.5-1 <https://bodhi.fedoraproject.org/updates/?search=valkey-7.2.5-1> > <https://bodhi.fedoraproject.org/updates/?search=valkey-7.2.5-1 <https://bodhi.fedoraproject.org/updates/?search=valkey-7.2.5-1>> > Thanks for the work on it. I wonder why valkey conflicts with redis, redict for instance does not!? Is this a decision for a preferred upgrade path? What about leaving this decision to the user (keydb, redict, valkey, redis on RHEL, etc) and allowing parallel installation for testing, decision making processes and migration.It is due to redict renaming some libs, while valkey has opted to retain "redis" on some lib file names.
It seems to be just links in the bin directory that overlaps (and not libs). Why not putting these links into the compat subpackage including also the conflict statement. That would allow to install the main package side-by-side to the other key-value-db forks.
-- Leon -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
