Enrico Scholz wrote:
Christopher Aillon <caillon@xxxxxxxxxx> writes:
I do not see how this matters here. rpm knows enough ways to handle it:
* explicit 'Requires: firefox = ...' in binary plugins
Packagers fall all too easily into the trap of >= and not updating the
min/max versions
It should be more or less trivial to write an rpmlint check which catches
'Requires: firefox >= ...'. A fedora packaging guideline for firefox
plugins can forbid this too.
That still doesn't solve the issue of firefox-foo requires firefox =
x.y.z and x.y.z+1 just came out to fix a security issue.
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
