Difference between revisions of "Software Collections"
m (WIP) |
m (WIP) |
||
| Line 33: | Line 33: | ||
== Usage of collections == | == Usage of collections == | ||
All below TBA | All below TBA | ||
| + | |||
=== Running an Executable from a Software Collection === | === Running an Executable from a Software Collection === | ||
| + | |||
| + | |||
=== Running a Shell Session with a Software Collection as Default === | === Running a Shell Session with a Software Collection as Default === | ||
| + | |||
=== Running a System Service from a Software Collection === | === Running a System Service from a Software Collection === | ||
| + | |||
=== Migrate from stock application stack to a collection === | === Migrate from stock application stack to a collection === | ||
Revision as of 06:50, 23 October 2014
About
For certain applications, more recent versions of some software components are often needed in order to use their latest new features. Software Collections provides a set of dynamic programming languages, database servers, and various related packages that are either more recent than their equivalent versions included in the base SME Server 9.x system.
Installation
One must enable the scl repository. See the Software Collections scl repository page on how to enable this repository.
After enabling the scl repo, the scl packages can be installed by issueing the following command:
yum install scl-utils scl-utils-build --enablerepo=scl
Installation of a collection
To get an overview of the available collections you can use the following command:
yum list available \* --disablerepo=* --enablerepo=scl
and to install a collection: (example)
yum install mariadb55 --enablerepo=scl
An overview of installed collections one can use:
scl -l
All collections will be installed in:
/opt/rh
as defined by:
/etc/scl/prefixes
Usage of collections
All below TBA
