[scl.org] rh-python36-build alternative in rhel

[Jiri Novak]

Hi,

pip is not preffered way for production deployments here. I'll keep it
as last resort (maybe even after adding the libraries into rh-python36
collection which is bad :))

But generally, if I want to create a dependent SCL, I obviously miss
some macros or something in the specfile.

thanks,
Gh.


Davis, Daniel (NIH/NLM) [C] wrote:
> Jiri, if you mean Python packages, I do it this way (for a designated
> owner account):
>
> scl enable rh-python36 bash
> pip install --user lxml
>
> Above, lxml is an example package.
>
> Also consider whether you want Python 36 binary extensions to always
> be available.   You can create a file in /etc/ld.so.conf.d that does
> that - SCLs don't do that to be safe about what else is on the box,
> but for your own boxes why not.
>
> Buried in ansible code, you can see this in action at
> https://GitHub.com/NLM-OCCS/occsab-python
> <https://GitHub.com/NLM-OCCS/occsab-python>
>
>
>
> Sent with BlackBerry Work (www.blackberry.com)
> ------------------------------------------------------------------------
> *From: *Jiri Novak <jiri.novak at ghorland.net>
> *Sent: *Nov 28, 2017 5:41 AM
> *To: *Stefan Ring <stefanrin at gmail.com>
> *Cc: *sclorg at redhat.com
> *Subject: *Re: [scl.org] rh-python36-build alternative in rhel
>
> Hi
>
> I need to add more libraries to rh-python36, which would require using
> rh-python36-build package and I've been told it is wring and I should do
> my own SCL.
>
> then I need to make the application use the extended SCL with added
> libraries.
>
> Just running it agains rh-python36 is not enough because of missing
> dependencies :(
>
> The specfile should create packages test-python36-build and
> test-python36-runtime as a collection that extends rh-python36
>
> Gh.
>
> Stefan Ring wrote:
> > On Tue, Nov 28, 2017 at 1:47 PM, Jiri Novak
> <jiri.novak at ghorland.net> wrote:
> >> Hi,
> >>
> >> according to this (
> >>
> https://developers.redhat.com/blog/2014/12/04/add-packages-to-python-2-7-software-collection/
> >> ), I'm trying to create my own extension of the rh-python36, though
> >> doesn't build:
> >>
> >> + '[' '%{buildarch}' = noarch ']'
> >> + QA_CHECK_RPATHS=1
> >> + case "${QA_CHECK_RPATHS:-}" in
> >> + /usr/lib/rpm/check-rpaths
> >> + /usr/lib/rpm/check-buildroot
> >> + '%{rh-python36_os_install_post}'
> >> /var/tmp/rpm-tmp.k3bzOV: line 316: fg: no job control
> >> error: Bad exit status from /var/tmp/rpm-tmp.k3bzOV (%install)
> >>
> >> most probably because the variables are not expanded?
> >> What did I miss? Specfile for refenrence in attachement.
> > What is this spec file? It looks awfully complicated.
> >
> > I'm getting you want to build something against rh-python36. Why don't
> > you take an existing package, let’s say, rh-python36-python-six, and
> > adapt it?
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/sclorg/attachments/20171128/7db4b1f8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 866 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/sclorg/attachments/20171128/7db4b1f8/attachment.sig>