Procedure 2.1. Converting a Conventional Spec File into a Software Collection Spec File

1. Add the %scl_package macro to the spec file. Place the macro in front of the spec file preamble as follows:

   %{?scl:%scl_package package_name}

2. You are advised to define the %pkg_name macro in the spec file in case the package is not built for the Software Collection:

   %{!?scl:%global pkg_name %{name}}

   Consequently, you can use the %pkg_name macro to define the original name of the package wherever it is needed in the spec file that you can then use for building both the conventional package and the Software Collection.
3. Change the Name tag in the spec file preamble as follows:

   Name: %{?scl_prefix}package_name

4. To check that all essential Software Collection's packages are dependencies of the main meta package, add the following macro after the BuildRequires or Requires tags in the spec file:

   %{?scl:Requires: %scl_runtime}

5. Edit the %setup macro in the %prep section of the spec file so that the macro can deal with a different package name in the Software Collection environment:

   %setup -q -n %{pkg_name}-%{version}

Procedure 2.3. Updating the PKG_CONFIG_PATH environment variable for %{_libdir}

1. To update the PKG_CONFIG_PATH environment variable for the %{_libdir} macro, create a custom script /etc/profile.d/name.sh. The script is preloaded when a shell is started on the system.
   For example, create the following file:

   %{?scl_prefix}pc-libdir.sh

2. Use the pc-libdir.sh short script that modifies the PKG_CONFIG_PATH variable to refer to your .pc files:

   export PKG_CONFIG_PATH=%{_libdir}/pkgconfig:/opt/provider/software_collection/path/to/your/pc_files

3. Add the file to your Software Collection package's spec file:

   SOURCE2: %{?scl_prefix}pc-libdir.sh

4. Install this file into the system /etc/profile.d/ directory by adjusting the %install section of the Software Collection package's spec file:

   %install
   install -p -c -m 644 %{SOURCE2} $RPM_BUILD_ROOT%{?scl:%_root_sysconfdir}%{!?scl:%_sysconfdir}/profile.d/

Procedure 2.4. Updating the PKG_CONFIG_PATH environment variable for %{_datadir}

1. To update the PKG_CONFIG_PATH environment variable for the %{_datadir} macro, create a custom script /etc/profile.d/name.sh. The script is preloaded when a shell is started on the system.
   For example, create the following file:

   %{?scl_prefix}pc-datadir.sh

2. Use the pc-datadir.sh short script that modifies the PKG_CONFIG_PATH variable to refer to your .pc files:

   export PKG_CONFIG_PATH=%{_datadir}/pkgconfig:/opt/provider/software_collection/path/to/your/pc_files

3. Add the file to your Software Collection package's spec file:

   SOURCE2: %{?scl_prefix}pc-datadir.sh

4. Install this file into the system /etc/profile.d/ directory by adjusting the %install section of the Software Collection package's spec file:

   %install
   install -p -c -m 644 %{SOURCE2} $RPM_BUILD_ROOT%{?scl:%_root_sysconfdir}%{!?scl:%_sysconfdir}/profile.d/

Procedure 2.5. Updating the MANPATH environment variable for the disabled Software Collection

1. To update the MANPATH environment variable, create a custom script /etc/profile.d/name.sh. The script is preloaded when a shell is started on the system.
   For example, create the following file:

   %{?scl_prefix}manpage.sh

2. Use the manpage.sh short script that modifies the MANPATH variable to refer to your man path directory:

   export MANPATH=${MANPATH:+${MANPATH}:}/opt/provider/software_collection/path/to/your/man_pages

3. Add the file to your Software Collection package's spec file:

   SOURCE2: %{?scl_prefix}manpage.sh

4. Install this file into the system /etc/profile.d/ directory by adjusting the %install section of the Software Collection package's spec file:

   %install
   install -p -c -m 644 %{SOURCE2} $RPM_BUILD_ROOT%{?scl:%_root_sysconfdir}%{!?scl:%_sysconfdir}/profile.d/

Procedure 2.6. Running regular tasks with cronjobs

1. To use cronjobs for running regular tasks, place a crontab file for your Software Collection in the /etc/cron.d/ directory with the Software Collection's name.
   For example, create the following file:

   %{?scl_prefix}crontab

2. Ensure that the contents of the crontab file follow the standard crontab file format, as in the following example:

   0 1 * * Sun root /opt/provider/software_collection/architecture/usr/bin/cron_job_name

3. Add the file to your spec file of the Software Collection package:

   SOURCE2: %{?scl_prefix}crontab

4. Install the file into the system directory /etc/cron.d/ by adjusting the %install section of the Software Collection package's spec file:

   %install
   install -p -c -m 644 %{SOURCE2} $RPM_BUILD_ROOT%{?scl:%_root_sysconfdir}%{!?scl:%_sysconfdir}/cron.d/
   

Procedure 2.7. Managing log files with logrotate

1. To manage your log files with logrotate, place a custom logrotate file for your Software Collection in the system directory for the logrotate jobs /etc/logrotate.d/.
   For example, create the following file:

   %{?scl_prefix}logrotate

2. Ensure that the contents of the logrotate file follow the standard logrotate file format as follows:

   /opt/provider/software_collection/var/log/your_application_name.log {
         missingok
         notifempty
         size 30k
         yearly
         create 0600 root root
     }

3. Add the file to your spec file of the Software Collection package:

   SOURCE2: %{?scl_prefix}logrotate

4. Install the file into the system directory /etc/logrotate.d/ by adjusting the %install section of the Software Collection package's spec file:

   %install
   install -p -c -m 644 %{SOURCE2} $RPM_BUILD_ROOT%{?scl:%_root_sysconfdir}%{!?scl:%_sysconfdir}/logrotate.d/