--------------------------------------------------------------------------------------
This file was created to explain some peculiarities of repositories used by the slpkg.
--------------------------------------------------------------------------------------


Default repositories:
---------------------
For -current users use sbo repository:
SlackBuilds.org (sbo) FAQ(15): 
Slackware current is not supported, but as a general rule, the scripts
should work on it as well.

Rworkman's (rlw) repository use dependencies where displayed in central site 
'http://rlworkman.net/pkgs/' and only those. Unfortunately there is no fixed reference
dependencies file PACKAGES.TXT.

Slackers.it (slackr) repository must be used only from Slackware64 current users
and has no reference dependencies.

Slackel.gr (slackl) repository must be used only from Slackware{x86, x86_64} current users.

MSB (msb) repository has one ChangeLog.txt file for three sub-repositories {1.6, 1.8, 1.10}.
So if you have updated the list of packages with version 1.8 and want to switch to version 
1.10 then run "slpkg upgrade" instead of "slpkg update". MSB (msb) repository has no reference 
dependencies.

Slonly repository do not support -current for x86 arch.

Studioware (studio), Alien's ktown (ktown), Alien's multilib (multi), Slacke E17 and E18
and Alien's restricted repository has no reference dependencies.

IMPORTANT: For Alien 's (Eric Hameleers) repositories (alien, multi and ktown) should run 
'slpkg upgrade' instant 'slpkg update', if you want to spend from -stable in -current or not
because there is not different file 'ChangeLog.txt' for each version.

Custom repositories:
--------------------
There is the possibility of adding the repository directly from the user enough to address
up to be the 'PACKAGES.TXT' files and 'CHECKSUMS.md5' least. If not is there for file 
'ChangeLog.txt' will get warning messages that the 'ChangeLog.txt' file can not be read but do
not worry, the process is completed normally have each time you run the command 'slpkg update'
the package lists for such a repository will be recreated from start automatically.

Sometimes you may experience some problems with these repositories such as the not correctly
resolve dependencies, and this may happen some specificities separate list which unfortunately
can not be calculated, good is the purpose of mentioning these problems.