From b76270bf9e6dd375e495fec92140a79a79415d27 Mon Sep 17 00:00:00 2001 From: Patrick J Volkerding Date: Wed, 19 May 2010 08:58:23 +0000 Subject: Slackware 13.1 Wed May 19 08:58:23 UTC 2010 Slackware 13.1 x86_64 stable is released! Lots of thanks are due -- see the RELEASE_NOTES and the rest of the ChangeLog for credits. The ISOs are on their way to replication, a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD. We are taking pre-orders now at store.slackware.com, and offering a discount if you sign up for a subscription. Consider picking up a copy to help support the project. Thanks again to the Slackware community for testing, contributing, and generally holding us to a high level of quality. :-) Enjoy! --- misc/slackbook/html/package-management.html | 148 ++++++++++++++++++++++++++++ 1 file changed, 148 insertions(+) create mode 100644 misc/slackbook/html/package-management.html (limited to 'misc/slackbook/html/package-management.html') diff --git a/misc/slackbook/html/package-management.html b/misc/slackbook/html/package-management.html new file mode 100644 index 000000000..e6ddc32b9 --- /dev/null +++ b/misc/slackbook/html/package-management.html @@ -0,0 +1,148 @@ + + + + +Slackware Package Management + + + + + + + + + + +
+

Chapter 18 Slackware Package +Management

+ + + +

A software package is a bundle of related programs that are ready for you to install. +When you download a source code archive, you have to configure, compile, and install it +by hand. With a software package, this has already been done for you. All that you have +to do is install the package. Another handy feature of using software packages is that it +is very easy to remove and upgrade them, if you so desire. Slackware comes with programs +for all your package management needs. You can install, remove, upgrade, make, and +examine packages very easily.

+ +

There's a myth that's been going around ever since RedHat debuted RedHat Package +Manager, that Slackware has no package management tool. This simply couldn't be further +from the truth. Slackware has always included a package manager, even before RedHat +existed. While not as full-featured or as ubiquitous as rpm (or for that matter deb), pkgtool and its associated programs are every bit as good at +installing packages as rpm. The truth about pkgtool is not that +it doesn't exist, but that it doesn't do any dependency checking.

+ +

Apparently many people in the Linux community think that a packager manager must by +definition include dependency checking. Well, that simply isn't the case, as Slackware +most certainly does not. This is not to say that Slackware packages don't have +dependencies, but rather that its package manager doesn't check for them. Dependency +management is left up to the sysadmin, and that's the way we like it.

+ +
+

18.1 Overview of Package Format

+ +

Before learning the utilities, you should become familiar with the format of a +Slackware package. In Slackware, a package is simply a tar archive file that has been +compressed with gzip. Packages are built to be extracted in the +root directory.

+ +

Here is a fictitious program and its example package:

+ + + + + +
+
+./
+usr/
+usr/bin/
+usr/bin/makehejaz
+usr/doc/
+usr/doc/makehejaz-1.0/
+usr/doc/makehejaz-1.0/COPYING
+usr/doc/makehejaz-1.0/README
+usr/man/
+usr/man/man1
+usr/man/man1/makehejaz.1.gz
+install/
+install/doinst.sh
+
+
+ +

The package system will extract this file in the root directory to install it. An +entry in the package database will be created that contains the contents of this package +so that it can be upgraded or removed later.

+ +

Notice the install/ subdirectory. This is a special +directory that can contain a postinstallation script called doinst.sh. If the package system finds this file, it will execute +it after installing the package.

+ +

Other scripts can be embedded in the package, but those are discussed more in detail +in Section +18.3.2 below.

+
+
+ + + + + -- cgit v1.2.3-65-gdbad