Adding more repositories

[gapan]

No, it is implicitly included. By specifying the main slackware repo, slapt-get knows to look into the patches directory as well.

[galmei]

http://docs.salixos.org/wiki/Can_I_use_ ... itories%3F

Hello gapan,
here is a hint for a small problem, because this hypertext link does not work. As protocol specification 'http' is included and the URL ends on '%3F'. If this URL is used, there is a change from 'http://' to 'https://'. The '%3F' is also replaced by a question mark, which is wrong because the question mark introduces the query string of the URL, as you know. With 'https://' in the URL it works, but there is something wrong somewhere, apart from the fact that an outdated protocol is given. Most Salix pages are actually delivered via 'https', I think.

[salix_user]

Useful info

Can I use slackpkg with Salix?

It is recommended that you use slapt-get/gslapt and not slackpkg. slackpkg is a package manager that was designed to manage packages from a single Slackware repository only.

Using slackpkg in Salix could cause (at least) some Salix (customized packages) to be replaced with their Slackware counterparts, which would remove the Salix customizations. Worse case scenario you could end up removing all Salix packages resulting in a mostly unusable system.

Can I use third party packages repositories?

Yes, of course you are free to add third party repositories (e.g. GSB, linuxpackages.net, alienbob...) to slapt-get, however, there may be issues.

It is important to remember that Salix does handle package dependencies, however, only for Salix & the 'special' Slackware repositories included in Salix default configuration for gslapt/slapt-get; not for any other third parties for whom we couldn't guarantee any sort of quality or compatibility control.

One is always free to direct gslapt/slapt-get to any third party package repositories. Keep in mind that third party repositories may not: handle dependencies, be of sufficient quality and may not be compatible with Salix. In such a case, you should know what you are doing because you may end up breaking your system.

Priorities are defined in the source code in this enumeration:
OFFICIAL have priority over DEFAULT. PREFERRED have priority over OFFICIAL. ....

Code: Select all

typedef enum {
    SLAPT_PRIORITY_DEFAULT = 0,
    SLAPT_PRIORITY_DEFAULT_PATCH,
    SLAPT_PRIORITY_OFFICIAL,
    SLAPT_PRIORITY_OFFICIAL_PATCH,
    SLAPT_PRIORITY_PREFERRED,
    SLAPT_PRIORITY_PREFERRED_PATCH,
    SLAPT_PRIORITY_CUSTOM,
    SLAPT_PRIORITY_CUSTOM_PATCH
} SLAPT_PRIORITY_T;

[gapan]

http://docs.salixos.org/wiki/Can_I_use_ ... itories%3F

Hello gapan,
here is a hint for a small problem, because this hypertext link does not work. As protocol specification 'http' is included and the URL ends on '%3F'. If this URL is used, there is a change from 'http://' to 'https://'. The '%3F' is also replaced by a question mark, which is wrong because the question mark introduces the query string of the URL, as you know. With 'https://' in the URL it works, but there is something wrong somewhere, apart from the fact that an outdated protocol is given. Most Salix pages are actually delivered via 'https', I think.

The https/http thing is not an issue, since http will always redirect to https on our servers. The questionmark thing is a problem with mediawiki. I won't deal with that now, since I have other plans for the wiki...