Difference between revisions of "Software Collections"
m (WIP) |
m (WIP) |
||
| Line 10: | Line 10: | ||
After enabling the scl repo, the scl packages can be installed by issueing the following command: | After enabling the scl repo, the scl packages can be installed by issueing the following command: | ||
| − | yum install scl-utils | + | yum install scl-utils --enablerepo=scl |
| Line 53: | Line 53: | ||
== Building your own software collections == | == Building your own software collections == | ||
| + | Please consider building your collection on non production systems only. | ||
| + | |||
| + | To be able to build your own software collection, an extra scl package has to be installed: | ||
| + | yum install scl-utils-build --enablerepo=scl | ||
[[Category:Howto]] | [[Category:Howto]] | ||
Revision as of 07:17, 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 --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
Collections will be installed in:
/opt/rh
as defined by the collection packager and noted here:
/etc/scl/prefixes
The one that build the software collection (called a provider) can tag his collections with a provider name. In the above case in '/opt/rh', the provider is Redhat. For SME Server this could be '/opt/sme' or personal collections e.g. '/opt/stephdl'
The /opt is the highly recommended installation location. However, in the case of SME Server, considerations to install in a different location could be considered regarding default backups etc. e.g. '/home/e-smith/files/scl/sme'.
Usage of collections
All below TBA
Running an Executable from a Software Collection
Running a Shell Session with a Software Collection as Default
Running a System Service from a Software Collection
Migrate from stock application stack to a collection
Examples
Building your own software collections
Please consider building your collection on non production systems only.
To be able to build your own software collection, an extra scl package has to be installed:
yum install scl-utils-build --enablerepo=scl
