On Tue, Feb 13, 2018 at 5:53 PM, Ben Nemec <openst...@nemebean.com> wrote:
> I guess if RDO has chosen this path then we don't have much choice.
This makes it sound like we had a choice to begin with.
We've already had a lot of discussions around the topic but we're
ultimately stuck between a rock and a hard place.
We're in this together and it's important that everyone understands
what's going on.
It's not a secret to anyone that Fedora is more or less the upstream to RHEL.
There's no py3 available in RHEL 7.
The alternative to making things work in Fedora is to use Software
If you're not familiar with Software Collections for python, it's more
or less the installation of RPM packages in a virtualenv.
Installing the "rh-python35" SCL would:
- Set up a chroot in /opt/rh/rh-python35/root
- Set up a py35 interpreter at /opt/rh/rh-python35/root/usr/bin/python3
And then, when you would install packages *against* that SCL, they
would end up being installed
That means that you need *all* of your python packages to be built
against the software collections and installed in the right path.
Python script with a #!/usr/bin/python shebang ? Probably not going to work.
Need python-requests ? Nope, sclo-python35-python-requests.
Need one of the 1000+ python packages maintained by RDO ?
Those need to be re-built and maintained against the SCL too.
If you want to see what it looks like in practice, here's a Zuul spec
file  or the official docs for SCL .
Making stuff work on Fedora is not going to be easy for anyone but it
sure beats messing with 1500+ packages that we'd need to untangle
Most of the hard work for Fedora is already done as far as packaging
is concerned, we never really stopped building packages for Fedora
It means we should be prepared once RHEL 8 comes out.
David Moreau Simard
Senior Software Engineer | OpenStack RDO
dmsimard = [irc, github, twitter]
OpenStack Development Mailing List (not for usage questions)