이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 2. Installation
This chapter describes in detail how to get access to the content set, install Red Hat Software Collections 3.8 on the system, and rebuild Red Hat Software Collections.
2.1. Getting Access to Red Hat Software Collections
The Red Hat Software Collections content set is available to customers with Red Hat Enterprise Linux subscriptions listed in the Knowledgebase article How to use Red Hat Software Collections (RHSCL) or Red Hat Developer Toolset (DTS)?. For information on how to register your system with Red Hat Subscription Management (RHSM), see Using Red Hat Subscription Management. For detailed instructions on how to enable Red Hat Software Collections using RHSM, see Section 2.1.1, “Using Red Hat Subscription Management”.
Since Red Hat Software Collections 2.2, the Red Hat Software Collections and Red Hat Developer Toolset content is available also in the ISO format at https://access.redhat.com/downloads, specifically for Server and Workstation. Note that packages that require the
Optional repository, which are listed in Section 2.1.2, “Packages from the Optional Repository”, cannot be installed from the ISO image.
Note
Packages that require the
Optional repository cannot be installed from the ISO image. A list of packages that require enabling of the Optional repository is provided in Section 2.1.2, “Packages from the Optional Repository”.
Beta content is unavailable in the ISO format.
2.1.1. Using Red Hat Subscription Management
If your system is registered with Red Hat Subscription Management, complete the following steps to attach the subscription that provides access to the repository for Red Hat Software Collections and enable the repository:
- Display a list of all subscriptions that are available for your system and determine the pool ID of a subscription that provides Red Hat Software Collections. To do so, type the following at a shell prompt as
root:subscription-manager list --availableFor each available subscription, this command displays its name, unique identifier, expiration date, and other details related to it. The pool ID is listed on a line beginning withPool Id. - Attach the appropriate subscription to your system by running the following command as
root:subscription-manager attach --pool=pool_idReplace pool_id with the pool ID you determined in the previous step. To verify the list of subscriptions your system has currently attached, type asroot:subscription-manager list --consumed - Display the list of available Yum list repositories to retrieve repository metadata and determine the exact name of the Red Hat Software Collections repositories. As
root, type:subscription-manager repos --listOr alternatively, runyum repolist allfor a brief list.The repository names depend on the specific version of Red Hat Enterprise Linux you are using and are in the following format:rhel-variant-rhscl-7-rpms rhel-variant-rhscl-7-debug-rpms rhel-variant-rhscl-7-source-rpms
Replace variant with the Red Hat Enterprise Linux system variant, that is,serverorworkstation. Note that Red Hat Software Collections is supported neither on theClientnor on theComputeNodevariant. - Enable the appropriate repository by running the following command as
root:subscription-manager repos --enable repository
Once the subscription is attached to the system, you can install Red Hat Software Collections as described in Section 2.2, “Installing Red Hat Software Collections”. For more information on how to register your system using Red Hat Subscription Management and associate it with subscriptions, see Using Red Hat Subscription Management.
Note
Subscription through RHN is no longer available.
2.1.2. Packages from the Optional Repository
Some of the Red Hat Software Collections packages require the
Optional repository to be enabled in order to complete the full installation of these packages. For detailed instructions on how to subscribe your system to this repository, see the relevant Knowledgebase article How to access Optional and Supplementary channels, and -devel packages using Red Hat Subscription Management (RHSM)?.
Packages from Software Collections for Red Hat Enterprise Linux that require the
Optional repository to be enabled are listed in the tables below. Note that packages from the Optional repository are unsupported. For details, see the Knowledgebase article Support policy of the optional and supplementary channels in Red Hat Enterprise Linux.
| Package from a Software Collection | Required Package from the Optional Repository |
|---|---|
| devtoolset-12-build | scl-utils-build |
| devtoolset-12-dyninst-testsuite | glibc-static |
| devtoolset-12-elfutils-debuginfod | bsdtar |
| devtoolset-12-gcc-plugin-devel | libmpc-devel |
| devtoolset-12-gdb | source-highlight |
| devtoolset-11-build | scl-utils-build |
| devtoolset-11-dyninst-testsuite | glibc-static |
| devtoolset-11-elfutils-debuginfod | bsdtar |
| devtoolset-11-gcc-plugin-devel | libmpc-devel |
| devtoolset-11-gdb | source-highlight |
| devtoolset-10-build | scl-utils-build |
| devtoolset-10-dyninst-testsuite | glibc-static |
| devtoolset-10-elfutils-debuginfod | bsdtar |
| devtoolset-10-gcc-plugin-devel | libmpc-devel |
| devtoolset-10-gdb | source-highlight |
| httpd24-mod_ldap | apr-util-ldap |
| rh-git227-git-cvs | cvsps |
| rh-git227-git-svn | perl-Git-SVN |
| rh-git227-perl-Git-SVN | subversion-perl |
| rh-php73-php-devel | pcre2-devel |
| rh-php73-php-pspell | aspell |
| rh-python38-python-devel | scl-utils-build |
2.2. Installing Red Hat Software Collections
Red Hat Software Collections is distributed as a collection of RPM packages that can be installed, updated, and uninstalled by using the standard package management tools included in Red Hat Enterprise Linux. Note that a valid subscription is required to install Red Hat Software Collections on your system. For detailed instructions on how to associate your system with an appropriate subscription and get access to Red Hat Software Collections, see Section 2.1, “Getting Access to Red Hat Software Collections”.
Use of Red Hat Software Collections 3.8 requires the removal of any earlier pre-release versions, including Beta releases. If you have installed any previous version of Red Hat Software Collections 3.8, uninstall it from your system and install the new version as described in the Section 2.3, “Uninstalling Red Hat Software Collections” and Section 2.2.1, “Installing Individual Software Collections” sections.>
The in-place upgrade from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 is not supported by Red Hat Software Collections. As a consequence, the installed Software Collections might not work correctly after the upgrade. If you want to upgrade from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7, it is strongly recommended to remove all Red Hat Software Collections packages, perform the in-place upgrade, update the Red Hat Software Collections repository, and install the Software Collections packages again. It is advisable to back up all data before upgrading.
2.2.1. Installing Individual Software Collections
To install any of the Software Collections that are listed in Table 1.1, “Red Hat Software Collections Components”, install the corresponding meta package by typing the following at a shell prompt as
root:
yum install software_collection...
Replace software_collection with a space-separated list of Software Collections you want to install. For example, to install rh-php73 and rh-mariadb105, type as
root:
~]# yum install rh-php73 rh-mariadb105
This installs the main meta package for the selected Software Collection and a set of required packages as its dependencies. For information on how to install additional packages such as additional modules, see Section 2.2.2, “Installing Optional Packages”.
2.2.2. Installing Optional Packages
Each component of Red Hat Software Collections is distributed with a number of optional packages that are not installed by default. To list all packages that are part of a certain Software Collection but are not installed on your system, type the following at a shell prompt:
yum list available software_collection-\*
To install any of these optional packages, type as
root:
yum install package_name...
Replace package_name with a space-separated list of packages that you want to install. For example, to install the rh-perl530-perl-CPAN and rh-perl530-perl-Archive-Tar, type:
~]# yum install rh-perl530-perl-CPAN rh-perl530-perl-Archive-Tar2.2.3. Installing Debugging Information
To install debugging information for any of the Red Hat Software Collections packages, make sure that the yum-utils package is installed and type the following command as
root:
debuginfo-install package_name
For example, to install debugging information for the rh-ruby27-ruby package, type:
~]# debuginfo-install rh-ruby27-ruby
Note that you need to have access to the repository with these packages. If your system is registered with Red Hat Subscription Management, enable the
rhel-variant-rhscl-6-debug-rpms or rhel-variant-rhscl-7-debug-rpms repository as described in Section 2.1.1, “Using Red Hat Subscription Management”. For more information on how to get access to debuginfo packages, see How can I download or install debuginfo packages for RHEL systems?.
2.3. Uninstalling Red Hat Software Collections
To uninstall any of the Software Collections components, type the following at a shell prompt as
root:
yum remove software_collection\*
Replace software_collection with the Software Collection component you want to uninstall.
Note that uninstallation of the packages provided by Red Hat Software Collections does not affect the Red Hat Enterprise Linux system versions of these tools.
2.4. Rebuilding Red Hat Software Collections
<collection>-build packages are not provided by default. If you wish to rebuild a collection and do not want or cannot use the
rpmbuild --define 'scl foo' command, you first need to rebuild the metapackage, which provides the <collection>-build package.
Note that existing collections should not be rebuilt with different content. To add new packages into an existing collection, you need to create a new collection containing the new packages and make it dependent on packages from the original collection. The original collection has to be used without changes.
For detailed information on building Software Collections, refer to the Red Hat Software Collections Packaging Guide.
