{% extends "section_about.html" %} {% block title %}Software Collections for Developers{% endblock %} {% block content %}
Collection prefix must be set to /opt/sclo
if hosting on SoftwareCollections.org is requested. All packages from SoftwareCollections.org will be installed into /opt/sclo
. Users have the possibility to redefine the path by adding the sclo-build package into their COPR buildroot. Other vendors must redefine it to their own vendor string.
An example SCL metapackage with an explanation of macros:
# check if builds are done on COPR %if 0%{?copr_username:1} # username and projectname will create unique prefix of project for COPR %global scl %{copr_username}-%{copr_projectname} %else # name of the collection e.g. ruby193 %global scl ruby193 %endif %scl_package %scl ...
Macros are defined in /etc/rpm/macros.scl
. It can be redefined there for local builds.
/opt/rh
by default in /etc/rpm/macros.scl
. It can be redefined there for local builds, but it can be also redefined in specfiles or by the sclo-build package./opt
) and scl_vendor (preset to rh
by upstream).An example SCL metapackage with a redefinition of the installation path for local builds:
%global %_scl_prefix /opt/scloor
# define a special directory if /opt is not sufficient %global %scl_basedir /mydir # define vendor string. The string should be registered in FHS. %global %scl_vendor mycompanyand continue as usual
%global scl ruby193 %scl_package %scl ...{% endblock %}