On 08. 02. 22 14:30, Jaroslav Mracek wrote:
> Rich dependencies are dynamic and they change from release to release
> (version macros, ...)
That is a different issue, and also happens for non-rich dependencies. I
think we agreed back when the Change was submitted that a dependency that
changed in any way (such as a version bump) shall always be treated as a new
dependency, did we not?
No we didn't and it will make the feature less usable - see reported issues
during testing in original request
(https://bugzilla.redhat.com/show_bug.cgi?id=1699672#c74
<https://bugzilla.redhat.com/show_bug.cgi?id=1699672#c74>).
Yes we did, see my immediate reply [1] below the comment you just linked, and
see my WIP change of the packaging guidelines [2].
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1699672#c76
[2] https://pagure.io/packaging-committee/pull-request/1144
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure
