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! --- .../html/package-management-making-packages.html | 120 +++++++++++++++++++++ 1 file changed, 120 insertions(+) create mode 100644 misc/slackbook/html/package-management-making-packages.html (limited to 'misc/slackbook/html/package-management-making-packages.html') diff --git a/misc/slackbook/html/package-management-making-packages.html b/misc/slackbook/html/package-management-making-packages.html new file mode 100644 index 000000000..f58127753 --- /dev/null +++ b/misc/slackbook/html/package-management-making-packages.html @@ -0,0 +1,120 @@ + + + + +Making Packages + + + + + + + + + +
+ + + + + + + + + + +
Slackware Linux Essentials
PrevChapter 18 Slackware Package +ManagementNext
+ +
+
+ +
+

18.3 Making Packages

+ +

Making Slackware packages can be either easy or difficult. There is no specific method +for building a package. The only requirement is that the package be a tar gzipped file +and if there is a postinstallation script, it must be /install/doinst.sh.

+ +

If you are interested in making packages for your system or for a network that you +manage, you should have a look at the various build scripts in the Slackware source tree. +There are several methods we use for making packages.

+ +
+

18.3.1 explodepkg

+ +

explodepkg(8) will do the same thing that installpkg does to extract the package, but it doesn't actually +install it and it doesn't record it in the packages database. It simply extracts it to +the current directory.

+ +

If you look at the Slackware source tree, you will see how we use this command for +“framework” packages. These packages contain a skeleton of what the final +package will look like. They hold all the necessary filenames (zero-length), permissions, +and ownerships. The build script will cat the package contents from the source directory +to the package build directory.

+
+ +
+

18.3.2 makepkg

+ +

makepkg(8) will package up the current directory into a valid +Slackware package. It will search the tree for any symbolic links and add a creation +block to the postinstallation script for creating them during the package install. It +also warns of any zero-length files in the package tree.

+ +

This command is typically run after you have created your package tree.

+
+ +
+

18.3.3 SlackBuild Scripts

+ +

Slackware packages are built in many different ways by necessity. Not all software +packages are written by their programmers to compile the same way. Many have compile time +options that are not all included in the packages Slackware uses. Perhaps you need some +of this functionality; you'll need to compile your own package then. Fortunately for many +Slackware packages, you can find SlackBuild scripts in the package's source code.

+ +

So what is a SlackBuild script? SlackBuild scripts are executable shell scripts that +you run as root to configure, compile, and create Slackware +packages. You can freely modify these scripts in the source directory and run them to +create your own versions of the default Slackware packages.

+
+
+ +
+
+ + + + + + + + + + + + +
PrevHomeNext
Package UtilitiesUpMaking Tags and Tagfiles (for setup)
+
+ + + -- cgit v1.2.3