Usage of slapt-get in Slint how-to
==================================

The file /etc/slapt-get/slapt-getrc lists software repositories from
which software packages can be downloaded by the slapt-get, gslapt and
spi packages managers.

You need to be root to edit the file file /etc/slapt-get/slapt-getrc
For any change in this file to take effect you should first update the
database with the following command, typed as root:
slapt-get -u

You can edit this file to include additional repositories or enable the
repository sbrepos provided by Eric Hameleers, not enabled by default,

To enable a disabled repository, remove the first character '#' of the
corresponding line.
To disable an enabled repository, insert a character '#' at the beginning
of the line.

Whenever packages with the same name are shipped in several
repositories, the package is installed:
   if available, from a CUSTOM repository, else
   if available, from a PREFERRED repository, else
   if available, from an OFFICIAL repository, else
   if available, from a DEFAULT repository
 
Each repository should end with a character ':' (after the last '/'),
followed by one of the words in capital letters above.

After having edited the file, type as root:
slapt-get -u
and check carefully the output to verify that your update has been
successfully applied.

To know which packages of a given name are available and in which
repositories, type its name in the search field of gslpat, or in a
terminal type as root:
slapt-get --search <pacakage name>

WARNINGS

Be aware that the packages in the repository extra-14.2 can occasionally
lack a dependency. If that happens, please report it in the Slint forum
or the Slint mailing list (links at the bottom of this document)
so that this be taken care of. This repository stores packages build
from SlackBuilds available @ https://slackbuilds.org but is not in sync
with it. If you want recent versions of packages in this repository use
the utility sbopkg to build and install up to date packages instead. 

Be aware that enabling several repositories can lead to unexpected results
as they could include packages with the same name but not the same content.
Only do that for a system not performing a critical mission and if you
really know what you are doing and are prepared to handle the conflicts
that could arise.

It is also recommended that all the dependencies of a package you install
come from the same repository, as the versions of these dependencies can
differ across repositories: the version of a package A already installed
could not fit a package B newly installed that needs A as dependency.

The repository sbrepos can contain packages and their dependencies also
included in the salix or extra-14.2 repository, but not at the same
version. If you enable it you might consider giving it a priority OFFICIAL
to favor it over the others (do not choose PREFERRED, this is reserved for
the Slint repository). Be aware though that this *could* lead to install
a package that is also dependency of another package coming from another
repository, but not at the version or with the content it expects.

Do not hesitate to request help for any issue in this Slint forum:
https://forum.salixos.org/viewforum.php?f=44
Or posting to the Slint mailing list (registration required):
https://slint.fr/blog/welcome-to-the-new-slint-mailing-list.html