>>>> "OP" == Orion Poplawski
<orion(a)nwra.com> writes:
OP> - Can we make epel7-py36 branches, and somehow have
OP> %python3_version, et. al. be 3.6 for those builds?
I can't think of any way to do that without extra magic. And if you
require something in the spec, you might as well just hardcode it.
OP> - Can we just make it easier for people to create python3X- packages
OP> from existing python3- or python3(X-n)- packages? And just drop the
OP> whole macro thing altogether, since sed -i -e s/pyton34-/python36-/
OP> *.spec does 90% of the work?
Right now the process is:
fedpkg request-repo --summary "Summary of foo" --exception python36-foo
fedpkg request-branch --repo python36-foo epel7
(wait)
fedpkg clone python36-foo
cd python36-foo
fedpkg retire "This is an EPEL-only package"
fedpkg switch-branch epel7
And then copy in your spec and sources, edit and go. There is no need
for a package review.
That's certainly a few steps but far from the worst process in the
distro. What could we do to make it easier?
- J<