On Tue, Oct 23, 2018 at 1:28 PM Jason L Tibbitts III <tibbs@xxxxxxxxxxx> wrote: > > >>>>> "OP" == Orion Poplawski <orion@xxxxxxxx> 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? > Wait, we can do that? I thought we couldn't use the exception process for this? -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
