Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

howtos:slackware_admin:how_to_use_slackware_installing_software [2012/09/25 04:12 (UTC)]
mfillpot moved from general howtos namespace
howtos:slackware_admin:how_to_use_slackware_installing_software [2014/03/15 12:24 (UTC)] (current)
alienbob Several enhancements, with input from maciuszek
Line 3: Line 3:
 ===== Overview ===== ===== Overview =====
  
-There are two basic ways to install software in Slackware: install a pre-build binary package, ​or make your own package. If you need to compile ​the package ​from source code, making it into your own package is easy and useful. Here's how both methods work.+There are three basic ways to install software in Slackware: install a pre-build binary package, make your own package, or compile the sources and install the resulting binaries manually. If you need to compile ​a program ​from source code, making it into your own package is easy and useful. Here's how these methods work.
  
 ===== Installing Pre-built Binary Packages ===== ===== Installing Pre-built Binary Packages =====
Line 10: Line 10:
  
   * Official packages can be found on the Slackware CD-ROM or the Slackware FTP/HTTP mirrors. The package browser can be found at  http://​packages.slackware.com/​.   * Official packages can be found on the Slackware CD-ROM or the Slackware FTP/HTTP mirrors. The package browser can be found at  http://​packages.slackware.com/​.
-  * Unofficial, community contributed binaries can be found at sites such as http://www.linuxpackages.net/http://www.slacky.eu ​and http://slackfind.net/. Usually ​the file name ends with ''​.tgz'',​ ''​.tbz''​ or ''​.txz''​ and looks something like "​mozilla-firefox-14.0-x86_64-1.txz"​. Make sure you get the Slackware package built with the correct architecture and made for your version of Slackware!+  * Unofficial, community contributed binaries can be searched for at http://slackfind.net/ which indexes the most well-known [[#​community_repositories|community repositories]] and Slackware-compatible spin-offs like http://​slacky.euhttp://salixos.organd more.\\ Usually ​a package ​file name ends with ''​.tgz''​ or ''​.txz''​ and looks something like "''​mozilla-firefox-14.0-x86_64-1.txz''​"​. ​The more universal naming scheme is "''​PRGNAM-VERSION-ARCH-BUILD.txz''"​ where ARCH denotes the architecture for which the package was built (examples are ''​x86_64'',​ ''​i486''​. ''​armv6l'',​ ''​armv7hl'',​ ''​noarch''​) and the BUILD number is not just used to mark incremental package updates but also allows community packagers to add their own //build tag//(( -Well-known tags are "​_SBo"​ (slackbuilds.org),​ "​alien"​ (Eric Hameleers), "​_rlw"​ (Robby Workman), "​ponce"​ (Matteo Bernardini)- )) which makes them unique.\\ ​Make sure you get the Slackware package built for the correct architecture and made for your version of Slackware!
  
-To install the package you need to change to the root user. Run either the command ''​su -''​ or ''​sudo ​bash''​ and enter your root password. Now run the command ​+To install the package you need to change to the root user. Run either the command ''​su -''​ or ''​sudo ​-i''​ and enter your root password. Now run the command ​
     upgradepkg --install-new your-long-package-file-name     upgradepkg --install-new your-long-package-file-name
     ​     ​
 You should see a bunch of text running across your screen telling you about the package being installed, and possibly about an old package it might be replacing. You should see a bunch of text running across your screen telling you about the package being installed, and possibly about an old package it might be replacing.
  
-===== Make Package =====+===== Make Package =====
  
 ====From Source==== ====From Source====
Line 23: Line 23:
 The recommended way to build packages from source is to use or create [[slackware:​slackbuild_scripts|SlackBuild scripts]]. ​ The recommended way to build packages from source is to use or create [[slackware:​slackbuild_scripts|SlackBuild scripts]]. ​
  
-However, there are other utilities such as [[http://​www.src2pkg.net/​|src2pkg]] and [[http://​asic-linux.com.mx/​~izto/​checkinstall/​|checkinstall]] which automate the package creation process entirely (with a few user inputs), but these are not guaranteed to work with all possible kinds of source projects.+However, there are other utilities such as [[http://​www.slackware.com/​~mozes/​|slacktrack]] (part of Slackware itself), ​[[http://​www.src2pkg.net/​|src2pkg]] and [[http://​asic-linux.com.mx/​~izto/​checkinstall/​|checkinstall]] which automate the package creation process entirely (with a few user inputs), but these are not guaranteed to work with all possible kinds of source projects. 
 ====From third-party package formats==== ====From third-party package formats====
  
 Binary packages from other distributions can be converted to Slackware packages by using conversion tools. Although building packages from source is always better, there are some situations which might warrant the use of these tools. Binary packages from other distributions can be converted to Slackware packages by using conversion tools. Although building packages from source is always better, there are some situations which might warrant the use of these tools.
  
-  * ''​rpm2tgz''​ can be used to convert .rpm packages to Slackware packages.+  * ''​rpm2tgz'' ​which is part of Slackware ​can be used to convert .rpm packages to Slackware packages.
   * [[http://​code.google.com/​p/​deb2tgz/​|deb2tgz]] converts .deb packages to Slackware packages.   * [[http://​code.google.com/​p/​deb2tgz/​|deb2tgz]] converts .deb packages to Slackware packages.
   * [[http://​joeyh.name/​code/​alien/​|alien]] is a tool used to convert packages to and from different distribution package formats.   * [[http://​joeyh.name/​code/​alien/​|alien]] is a tool used to convert packages to and from different distribution package formats.
 +
 ===== Compiling from scratch ===== ===== Compiling from scratch =====
  
Line 43: Line 45:
  
 Other build systems may involve different steps, depending on how the source project is set up. As always, it is best to read the upstream developer documentation to figure out how to compile and build a program for your system, including which dependencies to fulfill. Other build systems may involve different steps, depending on how the source project is set up. As always, it is best to read the upstream developer documentation to figure out how to compile and build a program for your system, including which dependencies to fulfill.
 +
 +===== Community Repositories ====
 +
 +  * Slackware Team:
 +    * Eric Hameleers [[http://​www.slackware.com/​~alien/​slackbuilds/​|regular packages]]; [[http://​www.slackware.com/​~alien/​restricted_slackbuilds/​|packages with patent restrictions]];​ [[http://​taper.alienbase.nl/​mirrors/​alien-kde/​|KDE bleeding edge]]; [[http://​www.slackware.com/​~alien/​multilib/​|multilib]]
 +    * [[http://​rlworkman.net/​pkgs/​|Robby Workman]]
 +  * Wider Community:
 +      * [[http://​www.droplinegnome.org/​|Dropline Gnome]]
 +      * [[http://​www.microlinux.fr/​mled.php|Micro Linux Enterprise Desktop (MLED)]]
 +      * [[http://​mateslackbuilds.github.io/​|MATE SlackBuilds (MSB)]]
 +      * [[http://​ponce.cc/​slackware/​|Ponce'​s Pimp My Slack]]
 +      * http://​slacky.eu/​
 +      * http://​salixos.org/​
 +
  
 ===== Sources ===== ===== Sources =====
    * Originally written by [[wiki:​user:​peterwwillis|peterwwillis]] for the SlackDocs Wiki Project    * Originally written by [[wiki:​user:​peterwwillis|peterwwillis]] for the SlackDocs Wiki Project
    * Additional contributions by [[wiki:​user:​vharishankar|V.Harishankar]]    * Additional contributions by [[wiki:​user:​vharishankar|V.Harishankar]]
 +   * Additional contributions by [[wiki:​user:​alienbob|Eric Hameleers]],​ with input from //​maciuszek//​
  
 {{tag>​howtos software installing package_management author_peterwwillis}} {{tag>​howtos software installing package_management author_peterwwillis}}

In Other Languages
QR Code
QR Code howtos:slackware_admin:how_to_use_slackware_installing_software (generated for current page)