Editing Slackware (section)

===Repositories===
There are no official repositories for Slackware. The only official packages Slackware provides are available on the installation media. However, there are many third-party repositories for Slackware; some are standalone repositories and others are for distributions that are Slackware-based but retain package compatibility with Slackware. Many of these can be searched at once using pkgs.org, which is a Linux package search engine. However, mixing and matching dependencies from multiple repositories can lead to two or more packages that require different versions of the same dependency, which is a form of [[dependency hell]]. Slackware itself won't provide any dependency resolution for these packages, however some projects will provide a list of dependencies that are not included with Slackware with the files for the package, commonly with a {{Mono|.dep}} extension.

Due to the possibility of dependency issues, many users choose to compile their own programs using community-provided SlackBuilds. SlackBuilds are shell scripts that will create an installable Slackware package from a provided software tarball. Since SlackBuilds are scripts, they aren't limited to just compiling a program's source; they can also be used to repackage pre-compiled binaries provided by projects or other distributions' repositories into proper Slackware packages. SlackBuilds that compile sources have several advantages over pre-built packages: since they build from the original author's [[source code]], the user does not have to trust a third-party packager; furthermore the local compilation process allows for machine-specific optimization. In comparison to manual compilation and installation of software, SlackBuilds provide cleaner integration to the system by utilizing Slackware's package manager. Some SlackBuilds will come with an additional file with metadata that allows automated tools to download the source, verify the source is not corrupt, and calculate additional dependencies that are not part of Slackware.<ref>{{cite web|url=https://slackbuilds.org/guidelines/#info|title=SlackBuilds.org|first=WebSight Designs -|last=websightdesigns.com|website=Slackbuilds.org|access-date=January 15, 2017|archive-date=January 16, 2017|archive-url=https://web.archive.org/web/20170116174913/https://slackbuilds.org/guidelines/#info|url-status=live}}</ref> Some repositories will include both SlackBuilds and the resulting Slackware packages, allowing users to either build their own or install a pre-built package.

The only officially endorsed<ref>{{cite web|url=http://www.linuxquestions.org/questions/slackware-14/slackware-14-2-is-coming-but-will-the-slackbuilds-will-also-be-updated-accordingly-4175575223/#post5517961|title=Slackware 14.2 is coming, but will the slackbuilds will also be updated accordingly?|website=Linuxquestions.org|access-date=March 19, 2016|archive-date=March 22, 2016|archive-url=https://web.archive.org/web/20160322090136/http://www.linuxquestions.org/questions/slackware-14/slackware-14-2-is-coming-but-will-the-slackbuilds-will-also-be-updated-accordingly-4175575223/#post5517961|url-status=live}}</ref> SlackBuilds repository is SlackBuilds.org, commonly referred to as SBo. This is a community-supported project offering SlackBuilds for building software not included with Slackware. Users are able to submit new SlackBuilds for software to the site and, once approved, they become the "package maintainer". They are then responsible for providing updates to the SlackBuild, either to fix issues or to build newer versions provided by [[Upstream (software development)|upstream]]. To ensure all programs can be compiled and used, any required dependencies of the software not included with Slackware are required to be documented and be available on the site. All submissions are tested by the site's administrators before being added to the repository. The administrators intend for the build process to be nearly identical to the way Slackware's official packages are built, mainly to ensure Volkerding was "sympathetic of our cause". This allows SlackBuilds that Volkerding deems worthy to be pulled into regular Slackware with minimal changes to the script. It also prevent users from suggesting Volkerding to change his scripts to match SBo's.<ref>{{cite web|url=http://alien.slackbook.org/blog/ten-years-of-slackbuilds-org/|title=Ten years of SlackBuilds.org|date=June 10, 2016|website=Alien.dslackbook.org|access-date=July 22, 2017|archive-date=August 3, 2017|archive-url=https://web.archive.org/web/20170803091637/http://alien.slackbook.org/blog/ten-years-of-slackbuilds-org/|url-status=live}}</ref> SBo provides templates<ref>{{cite web|url=https://slackbuilds.org/templates|title=Index of /templates|website=Slackbuilds.org|access-date=January 15, 2017|archive-date=January 18, 2017|archive-url=https://web.archive.org/web/20170118032729/https://slackbuilds.org/templates/|url-status=live}}</ref> for SlackBuilds and the additional metadata files and they encourage package maintainers to not deviate unless necessary.<ref>{{cite web|url=https://slackbuilds.org/guidelines/|title=WebSight Designsm|website=Slackbuilds.org|access-date=January 15, 2017|archive-date=January 16, 2017|archive-url=https://web.archive.org/web/20170116174913/https://slackbuilds.org/guidelines/|url-status=live}}</ref>

Two Slackware team members, Eric Hameleers and Robby Workman each have their own repository of pre-compiled packages along with the SlackBuilds and source files used to create the packages. While most packages are just additional software not included in Slackware that they felt was worth their time to maintain, some packages are used as a testbed for future upgrades to Slackware, most notably, Hameleers provides "Ktown" packages for newer versions of [[KDE]].<ref>{{cite web|url=http://alien.slackbook.org/ktown/|title=Index of /ktown|website=Alien.slackbook.org|access-date=January 15, 2017|archive-date=December 31, 2016|archive-url=https://web.archive.org/web/20161231121150/http://alien.slackbook.org/ktown/|url-status=live}}</ref> He also maintains Slackware's "multilib" repository, enabling Slackware64 to run and compile 32-bit packages.<ref name="multilib"/>