On 23. 09. 21 5:41, Orion Poplawski wrote:
-Requires: %{name}%{?_isa} = %{version}-%{release}
+Requires: utf8proc%{?_isa} >= %{version}-%{release}
I'd assume that anybody (even you) might need to rebuild this package in EPEL
at any time for various reasons and %{release} might be larger than the RHEL
package release. This >= requireement will break.
Also, if the RHEL version gets updated to e.g. 2.1.2 (unlikely, but not
impossible), the EPEL devel package will still be able to be installed, which
is probably undesired.
If you don't need to follow RHEL's release number that much, I suggest to do:
Requires: utf8proc%{?_isa} = %{version}
And if you do, I suggest to do:
%global rhel_release 5
Requires: (utf8proc%{?_isa} = %{version} with utf8proc%{?_isa} >=
%{version}-%{rhel_release})
You could even incorporate the RHEL's release to the EPEL's release, if you
feel like it:
%global rhel_release 5
%global base_release 1
Release: %{rhel_release}.%{base_release}%{?dist}
Side note: I also suggest to BuildRequire the runtime requirement (sans
%{?_isa}) and track the package in Koschei. That way, you can get a
notification if the requirement was broken by an RHEL update and the EPEL
package needs to be updated as well.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
