On Sun, 13 Dec 2020 at 13:17, Miro Hrončok mhroncok@redhat.com wrote:
On 12/13/20 7:03 PM, Orion Poplawski wrote:
On 12/13/20 10:37 AM, Orion Poplawski wrote:
On 12/11/20 5:04 PM, Miro Hrončok wrote:
On 12/12/20 12:12 AM, Troy Dawson wrote:
Seem reasonable? I was able to install the resulting qpdf-devel fine.
Don't forget to move the following metadata to the main package:
Summary: Development files for QPDF library Requires: qpdf-libs%{?_isa} = %{version}-%{release}
Do you mean the main package as qpdf ? We don't control that package.
Also, since you might want to bump the release independently in EPEL (e.g. if we discover something was wrong in the way we have packaged this), I recommend doing:
%global rhelrelease 10 %global baserelease 1 Release: %{rhelrelease}.%{baserelease}%{?dist} ... Requires: qpdf-libs%{?_isa} = %{version}-%{rhelrelease}%{?dist}
(Assuming qpdf has regular %{dist} and not some modularity artificial value.)
Note that I've named the EPEL part of the release "baserelease", so rpmdev-bumpspec does the right thing.
That makes sense.
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org 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@lists.fedoraproject...