> But, indeed, GCC 9 and 10 are the only ones maintained by RH
> and modularity is the new way (for now) to provides new
> versions of applications / languages.
Then there seems to be a need to maintain a parallel to AppStreams in a
distribution planned to mirror RHEL8, RockyLinux. I know yum is
CentOS 8 is not going to keep up with RHEL 8, and this is a big issue for many
systems groups. You should read up on that to see how that affects you.
The latest for CentOS 7 are in http://mirror.centos.org/centos-7/7/sclo/. I
think the site is frozen in time, not really abandoned.
On 5/10
If you want scl enable to effect the ansible process itself, you could write a
python function that parses the enable script using shutil and then sets the
environment variables on os.environ. Then, expose this as an ansible plugin.
From: sclorg-boun...@redhat.com On Behalf Of Rob
Wissmann
Se
Finally got it. Please forgive my long emails:
https://www.softwarecollections.org/en/docs/guide/#sect-Building_a_Software_Collection_Locally
rpmbuild -ba python-pymongo.spec --define 'scl rh-python36'
From: sclorg-boun...@redhat.com On Behalf Of Davis,
Daniel (NIH/NLM) [C]
Se
/sect-extending_the_python27_and_python33_software_collections
From: sclorg-boun...@redhat.com On Behalf Of Davis,
Daniel (NIH/NLM) [C]
Sent: Monday, July 22, 2019 3:53 PM
To: sclorg@redhat.com
Subject: Re: [scl.org] rh-python36 and sqlite version
I've downloaded rh-python36-python-pymongo-3.5.1-1.el7.src.rpm and I see the
macro
c --define "%scl_python rh-python36
%scl_prefix_python rh-python36-"
The changes should only be in the spec. file, which I've already pulled out.
Can someone confirm?
From: sclorg-boun...@redhat.com On Behalf Of Davis,
Daniel (NIH/NLM) [C]
Sent: Monday, July 22, 2019 3:37 PM
To:
I recently noticed that Django 2.2 requires sqlite 3.8.3 or better. I first
tried the Fedora 26 SRPM, and then the Fedora 23 SRPM.
I needed to make one tweak to the later:
https://github.com/danizen/sqlite-centos7
Problem with my method, which I long ago honed when shipping a custom
applianc
Nick,
Now that your question has been answered, let me ask mine.The instructions
to build pyscl-devel separate from Copr are not clear enough for me. Are you
suggesting that I run pipsi in a virtual environment?How is scrlo-python
involved?
I'm going to try later today, and want to b
It might be nice to provide an sclo-python35 and sclo-python36 so that users
such as we have an easier time not updating. I hope we will not for a long
time be in the situation between python 2.7 and python 3, but it could happen
between 36 and 37 for any of a number of reasons. However, tha
t.com]
Sent: Tuesday, July 11, 2017 4:45 AM
To: Davis, Daniel (NIH/NLM) [C]
Cc: sclorg@redhat.com
Subject: Re: [scl.org] Python "latest" SCLo
On Mon, Jul 3, 2017 at 3:47 PM, Nick Coghlan wrote:
> On Fri, Jun 30, 2017 at 1:24 AM, Davis, Daniel (NIH/NLM) [C]
> wrote:
>> I’v
Sent: Thursday, June 29, 2017 12:52 PM
To: Davis, Daniel (NIH/NLM) [C] ; sclorg@redhat.com
Subject: Re: [scl.org] Python "latest" SCLo
Yes, thanks Dan. Many security scanning tools look for the latest version and
flag older versions as being a potential risk. I wanted to be sure that
The DevOps team wants to update to the latest Python as a rule as a security
from security mitigation technique.I hope that makes sense.
From: Brian Gollaher [mailto:bgoll...@redhat.com]
Sent: Thursday, June 29, 2017 11:50 AM
To: Davis, Daniel (NIH/NLM) [C] ; sclorg@redhat.com
Subject: Re
I've been lurking on this list for a while, and I wanted to bring myself up to
date. I noticed some talk of a community SCL for a "latest" Python, which
would be a non-patched pure build of Python that is kept up-to-date by the
community. Where is that at? Who is leading it? How can I he
Amen to this. I shipped an appliance install base on Pungi/Anaconda, but in
my current role, I do not have root.
I found SCL and got what we needed without us having to build it ourself.
-Original Message-
From: sclorg-boun...@redhat.com [mailto:sclorg-boun...@redhat.com] On Behalf Of
For the python SCLs, I would potentially love this, but one would need to be
careful to version the wrappers/symlinks, and/or worry about rpaths and ld
config.
To be more specific - one problem I've had is running a testing tool called
"tox" - the idea is that "tox" runs your python code with m
Noah,
You can find them here - http://mirror.centos.org/centos/7/sclo/x86_64/rh/, and
that is the new home.
Note also that rh-python35 is not available for CentOS 6, e.g. not here -
http://mirror.centos.org/centos/6/sclo/x86_64/rh/, the new home for that.
--Dan
-Original Message-
From:
t.com]
Sent: Thursday, June 09, 2016 2:41 PM
To: Davis, Daniel (NIH/NLM) [C]
Cc: sclorg@redhat.com
Subject: Re: [scl.org] Problems with Python scripts that use SCL runtimes
On Thu, Jun 9, 2016 at 7:59 AM, Davis, Daniel (NIH/NLM) [C]
wrote:
> Nick,
>
> We also encountered this issue, and we
Nick,
We also encountered this issue, and we wished DevOps and developers not to have
the issue.
So, our development users, DevOps account, and CI account all have in their
~/.bash_profile:
test -f /opt/rh/rh-python34/enable && source /opt/rh/rh-python34/enable
This enable script is di
18 matches
Mail list logo
