On Mon, Apr 11, 2016 at 3:35 PM, Dave Johansen <[email protected]> wrote:
> On Mon, Apr 11, 2016 at 1:09 PM, Jason L Tibbitts III <[email protected]> > wrote: > >> >>>>> "DJ" == Dave Johansen <[email protected]> writes: >> >> DJ> Is there anything that could be done in EPEL to make the Python 3 >> DJ> macros be usable without requiring %{python3_pkgversion}? >> >> Well, there has been some on and off work focused on making python >> packaging less hideous. A spec would look sort of like this: >> >> https://pagure.io/python-macros/blob/master/f/test1.spec >> >> And I think that would work down into EPEL. >> > > Good to hear that progress is being made. > > >> But otherwise, there's not much we can do about that _pkgversion macro, >> since EPEL may even get multiple python versions at some point. The >> fancy macros actually handle that, but they aren't really a thing you >> could use right now. >> > > For the time being, could the python34 package add a Provides for python3 > so the _pkgversion macro isn't necessary? > Or maybe even better, could there be a python3 package in EPEL that is just a set of Requires to act as a sort of "alias" to the python3x packages?
_______________________________________________ epel-devel mailing list [email protected] http://lists.fedoraproject.org/admin/lists/[email protected]
