Excerpts from Bohuslav Kabrda's message of 2015-03-02 21:59 +10:00: > ----- Original Message ----- > > Under the current proposal every package with Python 3 dependencies > > would have to depend on a specific python3x-* package, so then it would > > be up to the maintainers of all those packages to manually bump their > > Requires from python34-* to python35-* at some point. Which, now that > > I think about it, is not that great. Even worse, if any packages form > > a transitive dependency chain then *all* packages in the chain have to > > update their Requires at the same time to avoid having a mix of > > python34-* and python35-* requirements. > > Not really. The requires/buildrequires should be in form of > Requires: python%{python3_pkgversion}-six > so when we change %python3_pkgversion in the minimal buildroot, > maintainer just rebuilds and gets updated requires.
Hmm okay. I didn't realise this. So that means that: * Fedora specfiles can't be used unchanged (they will require python3-*, needs to have %{python3_pkgversion} macro inserted) * applications will need to be rebuilt to pick up a change from python34-* to python35-* which is a bit unfortunate. Is there any reason why we shouldn't just upgrade applications to the python35-* stack straight away, by providing python3-*? -- Dan Callaghan <dcall...@redhat.com> Software Engineer, Hosted & Shared Services Red Hat, Inc.
signature.asc
Description: PGP signature
_______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel