[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| wiki:user:kikinovak [2014/01/29 10:57 (UTC)] – Continued translation of "Software Management" article kikinovak | wiki:user:kikinovak [2014/02/09 15:21 (UTC)] – kikinovak | ||
|---|---|---|---|
| Line 47: | Line 47: | ||
| Stuff I'm currently working on, and which will eventually end up as a page in the Slackware Documentation Project. | Stuff I'm currently working on, and which will eventually end up as a page in the Slackware Documentation Project. | ||
| - | ===== Software Management ===== | ||
| - | ==== Anatomy of a Slackware package ==== | ||
| - | A Slackware package is a simple TGZ or TXZ compressed archive containing: | ||
| - | * the tree structure of files and directories ; | ||
| - | * post-installation scripts ; | ||
| - | * the package description. | ||
| - | |||
| - | The name of every package provides a series of informations: | ||
| - | |||
| - | * the program name ; | ||
| - | * the program version ; | ||
| - | * the architecture of the package ; | ||
| - | * the build number. | ||
| - | |||
| - | Here's a few examples: | ||
| - | |||
| - | * '' | ||
| - | * '' | ||
| - | * '' | ||
| - | |||
| - | ==== Managing Slackware packages using the traditional tools ==== | ||
| - | |||
| - | Since its early releases, Slackware provides a collection of simple tools - the '' | ||
| - | |||
| - | * '' | ||
| - | * '' | ||
| - | * '' | ||
| - | * '' | ||
| - | * '' | ||
| - | |||
| - | === Installing software packages === | ||
| - | |||
| - | Install the Emacs editor from the Slackware DVD ((if it's not already installed)): | ||
| - | |||
| - | < | ||
| - | # mount /dev/cdrom /mnt/cdrom | ||
| - | # cd / | ||
| - | # installpkg emacs-24.2-i486-1.txz | ||
| - | Verifying package emacs-24.2-i486-1.txz. | ||
| - | Installing package emacs-24.2-i486-1.txz [ADD]: | ||
| - | PACKAGE DESCRIPTION: | ||
| - | # emacs (GNU Emacs) | ||
| - | # | ||
| - | # Emacs is the extensible, customizable, | ||
| - | # display editor. If this seems to be a bit of a mouthful, an | ||
| - | # easier explanation is that Emacs is a text editor and more. At | ||
| - | # its core is an interpreter for Emacs Lisp, a dialect of the Lisp | ||
| - | # programming language with extensions to support text editing. | ||
| - | # This version supports X. | ||
| - | # | ||
| - | # http:// | ||
| - | # | ||
| - | Executing install script for emacs-24.2-i486-1.txz. | ||
| - | Package emacs-24.2-i486-1.txz installed. | ||
| - | </ | ||
| - | |||
| - | <note tip>If you're using the CD set, Emacs is on the first CD.</ | ||
| - | |||
| - | === Checking if a package is installed === | ||
| - | |||
| - | The package installation process has created a new entry in ''/ | ||
| - | |||
| - | < | ||
| - | # ls / | ||
| - | / | ||
| - | </ | ||
| - | |||
| - | Knowing if a package is installed boils down to checking the existence of the corresponding entry in ''/ | ||
| - | |||
| - | < | ||
| - | # ls / | ||
| - | / | ||
| - | </ | ||
| - | |||
| - | Firefox is installed on the system, in version 15.0.1. Another example : | ||
| - | |||
| - | < | ||
| - | # ls / | ||
| - | ls: cannot access / | ||
| - | </ | ||
| - | |||
| - | There is no '' | ||
| - | |||
| - | === Removing a package === | ||
| - | |||
| - | Use '' | ||
| - | |||
| - | < | ||
| - | # removepkg emacs | ||
| - | </ | ||
| - | |||
| - | It's also possible to provide the complete name as an argument. In that case, it's better to call the command from within ''/ | ||
| - | |||
| - | < | ||
| - | # cd / | ||
| - | # removepkg emacs-24.2-i486-1 | ||
| - | </ | ||
| - | |||
| - | === Upgrading a package === | ||
| - | |||
| - | Slackware provides security updates for its latest releases. Visit the official site to know more about the latest updates: | ||
| - | |||
| - | < | ||
| - | # links http:// | ||
| - | </ | ||
| - | |||
| - | - Follow the '' | ||
| - | - Check out '' | ||
| - | - Read the file '' | ||
| - | |||
| - | You can also use the Links browser to fetch updates manually. Before launching Links, create a ''/ | ||
| - | |||
| - | < | ||
| - | # cd | ||
| - | # mkdir updates | ||
| - | # cd updates/ | ||
| - | # links mirrors.slackware.com | ||
| - | </ | ||
| - | |||
| - | - Follow the '' | ||
| - | - Check out the directory corresponding to your release and architecture. | ||
| - | - Change into the '' | ||
| - | - Download any available updates. | ||
| - | | ||
| - | Quit Links and install your updates like this : | ||
| - | |||
| - | < | ||
| - | # upgradepkg bind-9.9.1_P4-i486-1_slack14.0.txz | ||
| - | |||
| - | +============================================================================== | ||
| - | | Upgrading bind-9.9.1_P3-i486-1 package using ./ | ||
| - | +============================================================================== | ||
| - | Pre-installing package bind-9.9.1_P4-i486-1_slack14.0... | ||
| - | Removing package / | ||
| - | --> Deleting / | ||
| - | --> Deleting / | ||
| - | --> Deleting / | ||
| - | ... | ||
| - | Verifying package bind-9.9.1_P4-i486-1_slack14.0.txz. | ||
| - | Installing package bind-9.9.1_P4-i486-1_slack14.0.txz: | ||
| - | PACKAGE DESCRIPTION: | ||
| - | bind (DNS server and utilities) | ||
| - | # | ||
| - | # The named daemon and support utilities such as dig, host, and | ||
| - | # nslookup. | ||
| - | # nameserver are included. | ||
| - | # setup can be found in / | ||
| - | # | ||
| - | Executing install script for bind-9.9.1_P4-i486-1_slack14.0.txz. | ||
| - | Package bind-9.9.1_P4-i486-1_slack14.0.txz installed. | ||
| - | | ||
| - | Package bind-9.9.1_P3-i486-1 upgraded with new package | ||
| - | ./ | ||
| - | </ | ||
| - | |||
| - | Another example : | ||
| - | |||
| - | < | ||
| - | # upgradepkg iptables-1.4.14-i486-2_slack14.0.txz | ||
| - | </ | ||
| === Know more about the contents of a package === | === Know more about the contents of a package === | ||
| Line 452: | Line 292: | ||
| </ | </ | ||
| - | ==== Recompiler des paquets officiels | + | ==== Rebuild official packages |
| + | |||
| + | Slackware provides the entire system' | ||
| - | Slackware fournit le code source | + | * the source |
| + | * its fabrication recipe in the shape of a '' | ||
| + | * the package description in a '' | ||
| + | * eventually, a post-installation script named '' | ||
| + | * various other files like patches, custom menu entries, etc. | ||
| - | * le code source | + | === Build a package from source |
| - | * sa recette de fabrication sous forme de fichier '' | + | |
| - | * le descriptif du paquet, nommé '' | + | |
| - | * parfois, un fichier post-installation nommé '' | + | |
| - | * d' | + | |
| - | === Fabriquer un paquet à partir du code source | + | In the example below, we will build the '' |
| - | Dans l' | + | <note warning> |
| < | < | ||
| Line 470: | Line 312: | ||
| </ | </ | ||
| - | Choisir un endroit pour ranger le code source | + | Choose an appropriate place on your system to store the source |
| < | < | ||
| # cd | # cd | ||
| # mkdir -pv source/ | # mkdir -pv source/ | ||
| - | mkdir: | + | mkdir: |
| - | mkdir: | + | mkdir: |
| # cd source/ | # cd source/ | ||
| # links mirrors.slackware.com | # links mirrors.slackware.com | ||
| </ | </ | ||
| - | Récupérer le contenu de '' | + | Fetch the content from the '' |
| < | < | ||
| Line 491: | Line 333: | ||
| </ | </ | ||
| - | Rendre le fichier | + | Make the '' |
| < | < | ||
| Line 498: | Line 340: | ||
| </ | </ | ||
| - | Le script | + | The script |
| < | < | ||
| Line 504: | Line 346: | ||
| </ | </ | ||
| - | Il ne reste plus qu'à installer ce paquet | + | Now we can install the resulting package: |
| < | < | ||
