>>>>> "P" == Peter <pe...@pajamian.dhs.org> writes:
P> I would be worried, though, that you'll have packages that were built P> against python that are now trying to pull in and possibly run on P> python2 unnecessarily, and possibly detrimentally if Red Hat suddenly P> decides to push python2 packages out. I can't imagine a situation where that would happen. Perhaps you could give an example which you believe I haven't provided an accounting already. P> It seems to me that if the package is going to be built against P> pythin then it should require python, if it has to be built against P> python2 then it should require python2. I'm not understanding the issue here. python _is_ python2 and that isn't going to change for RHEL7 within its lifetime unless Red Hat really does bizarre things, and then we'd adapt. I just don't see Red Hat going so significantly against established Fedora packaging guidelines here. (Any package that needs the python3 version of something absolutely must require python3-something. It will never be acceptable for it to depend on python-something and expect that to be python3.) P> In neither case does it seem prudent to be tricking packages into P> thinking that python is actually python2. I don't see how anything is being tricked anywhere. This is adding just one thing: allow you to access python-foo via the package name python2-foo so that we don't have to have ifdefs. - J< _______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
