Have you wanted to use software collections but found packaging has kept you at bay? Tried rebuilding a package only to find it give you weird errors you’ve not seen before? In this blog post we’ll learn how to configure and use mock to build RPM packages for the Python 2.7 Software Collection. Along the way we’ll learn why we can’t use standard mock configurations, and what makes Software Collections (SCL) mock configurations different.
As Software Collections are getting popular, there are more and more people asking how they can build their own collections and/or extend collections in RHSCL. In this article, I will demonstrate how to extend python27 collection from RHSCL 1.2, adding a simple Python extension library. (Note that the same steps can be applied to the python33 collection.) I’m going to work on a RHEL 6 machine throughout this whole tutorial. I’m assuming that readers have basic knowledge of RPM building and Software Collections concept.
We recently announced that we’ve made available a set of Dockerfiles for Red Hat Software Collections. We are making these available since we think they may be useful to customers looking to build more complex application containers on top of RHEL and RHSCL. We don’t intend the Dockerfiles to produce useful standalone images which you’ll immediately put in production – the Docker images which these create are very simple containers which give you RHEL plus the basic set of packages from a particular RHSCL collection.
There are two different ways to get your hands on the Dockerfiles:
Red Hat’s David Egts has assembled this handy article on how to get started with open source.
Open source code drives collaborative innovation from a larger pool of developers at a lower cost, which is why federal agencies are adopting the “open source first” model. In fact Sonny Hashmi, CIO of the General Services Administration, recently announced that implementing open source software is among his top priorities this year.
So what’s the best way to increase your agency’s adoption of open source software and keep it secure? Here are six tips to get you there:
Like most programmers, I find it much easier to take some existing example of code and modify it to do what I want. Sometimes, I end up with nothing from the original source, but I still find it easier. I wonder if this is akin to writing where, I find, if you put the words down in a stream of consciousness manner, then “rewrite, rewrite, rewrite.”