> One thing that comes to mind is that while the Provides: change would be
> backward compatible, the Requires: change would not. New packages would be
> generated with Requirements that existing packages wouldn't satisfy, which
> would require a "rebuild the world" deployment that obsoletes most existing
> rpm packages. I'm sure there will be push-back against that.
That's the annoying thing with any dependency improvements, you need to do them
in phases - provides pre-populated preferably on a mass-rebuild and only then
enable the require-side. So there will need to be some kind of disable/enable
control for the thing.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2372#issuecomment-1409853764
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2372/c1409853...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
