Pulp

https://github.com/pulp/packaging/pull/35

I was reading on epel-devel this morning and I read this[0] which identifies that RHSCL is a product versus softwarecollections.org which is like EPEL but for software collections. Which one of these is our SCL work being based on?

[0]: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/M4ACZBF3SK6R6FMIZSHI5W4HRZYKQ5BP/

Yes, there are two repositories with software collections in them. There's Red Hat's official software collection, and then there's the softwarecollections.org's software collections.

A quick way of explaining it is the RH software collections are the base, and softwarecollection.org's are extras, much like the epel's relationship to base packages.

pulp-scl is dependent on the rh-python35(0) software collection supported/supplied by Redhat, as this is the only python3.5 software collection. This will be updated to rh-python36 when that is released

If/when an el6 collection is created, it will be dependent upon rh-python34 (the last python3 on el6)

Pulp's scl itself will not live in either of those, as it is product-specific to pulp and will live within our current distribution streams for packages (i.e. copr(1) )

(0) https://www.softwarecollections.org/en/scls/rhscl/rh-python35/
(1) https://copr.fedorainfracloud.org/coprs/g/pulp/scl/

Thanks pcreech. That is helpful. OK so now I'm left with a couple of confirmation questions.

1. It sounds like we'll be distributing our scl side-by-side our other Pulp bits. Is that right? That sounds good, but I wanted to check my understanding.

2. Is the pulp-scl just going to be one big rpm?

1. Sure! With the caveat of this is all NEW stuff for pulp3, and those decisions haven't been 100% talked about or made officially. This task is really focused on just creating the official collection after the first proof of concept, not distributing it

2. No! It will be multiple rpms. The short explanation is pulp-scl{,-build,-sclbuild,-runtime} are just rpms for setting up the SCL environment. There will be other rpms that are built in the environment, like is done in the python scl(0) that are the python packages we will use.

For more questions on scl's in general, I highly recommend experimenting with them and using them.

(0)http://bay.uchicago.edu/centos-vault/centos/7/sclo/Source/rh/rh-python35/

All that sounds good, thanks pcreech!

https://github.com/pulp/packaging/pull/36