Difference between revisions of "Software Collections"
Line 22: | Line 22: | ||
yum list available \* --disablerepo=* --enablerepo=scl-php54 | yum list available \* --disablerepo=* --enablerepo=scl-php54 | ||
− | php54 will be listed, and | + | php54 will be listed, and to install that version: |
yum install php54 --enablerepo=scl-php54 | yum install php54 --enablerepo=scl-php54 | ||
Revision as of 17:29, 1 February 2015
Is this article helpful to you?
Please consider donating or volunteering
Thank you!
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. Software Collections is only available for SME Server 9.x 64-bit
Installation
One must enable the Software Collections Repositories. See the Software Collections Repositories page on how to enable this repository.
After enabling the Software Collections repo, the scl packages can be installed by issuing the following command:
yum install scl-utils
Installation of a collection
All Software Collections (Applications) of Red Hat are available from here: https://www.softwarecollections.org/en/scls/ and their respective repo's from here: https://www.softwarecollections.org/repos/rhscl/
To be able to install a Software Collection, one must enable the respective repo. As an example, we will install PHP 5.4. To list all available version the following command can be used:
yum list available \* --disablerepo=* --enablerepo=scl-php54
php54 will be listed, and to install that version:
yum install php54 --enablerepo=scl-php54
Once installation is done, you can verify installed Software Collections by issuing:
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'.
For more information on running applications and other options please see the Software Collections Documentation
Usage of collections
Please see the individual application articles:
Building your own software collections
Please consider building your collection on non production systems only. For a full reference please refer to the developers manual here.
To be able to build your own software collection, an extra scl package has to be installed:
yum install scl-utils-build --enablerepo=scl
Contrib development
Development of a contrib for SCL PHP specifically is under way. Currently it is in (pre) Alpha stage. You can read more about it on the forums
References
Other articles in this category
Mysql57, PHP Software Collections, Software Collections, Software Collections Repositories, Software Collections:MariaDB, Software Collections:MongoDB, Software Collections:MySQL, Software Collections:MySQL55, Software Collections:Nodejs, Software Collections:PHP, Software Collections:PostgreSQL, Software Collections:Python, Software Collections:Ruby on Rails