Difference between revisions of "Software Collections"
(Adds example) |
|||
| Line 6: | Line 6: | ||
With Software Collections, you can build and concurrently install multiple versions of the same software components on your system. Software Collections have no impact on the system versions of the packages installed by any of the conventional RPM package management utilities. | With Software Collections, you can build and concurrently install multiple versions of the same software components on your system. Software Collections have no impact on the system versions of the packages installed by any of the conventional RPM package management utilities. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== More == | == More == | ||
Revision as of 14:19, 16 May 2014
Intro[edit | edit source]
Software Collections are for installing multiple (newer) versions of software like Python or Perl than the version distributed with the RedHat Enterprise Linux (RHEL) distribution you have.
Software Collections is like the virtualenv system for Python. So if you want Python 2.7 on your RHEL 6.x box, you can choose to use virtualenv for Python, or you can use Software Collections for Python and more (like Postgres, Nodejs, MariaDB, etc.).
With Software Collections, you can build and concurrently install multiple versions of the same software components on your system. Software Collections have no impact on the system versions of the packages installed by any of the conventional RPM package management utilities.
More[edit | edit source]
This is a part of the Python deployments series
