[ale] Slackware Packaging

[Ben Coleman]

On Fri, 21 Nov 2003 17:05:02 -0500 (EST), attriel wrote:

>I've done the compile, and I know I do a 'makepkg' to finish it
>
>I'm just not sure what I do in-between, since 'makepkg' says it'll take
>"the current directory (structure) and tar it for the package", meaning I
>obviously can't just go and install the compile, b/c then there'll be all
>the OTHER junk thats not rightfully part of mysql :o

The normal middle step is to figure out a way to have 'make install'
(or the equivalent) for the package run with a specified directory
acting as /.  E.g., if a normal install would put binaries in /usr/bin,
and your specified directory is /tmp/newpkg/, the modified install
would put binaries in /tmp/newpkg/usr/bin/.  Then you can run makepkg
in the /tmp/newpkg/ to make the package.

*How* you do it will be package-dependent.  Some packages have this
kind of install built-in, some don't.  In the latter case, you may need
to modify the make files yourself.

If you're recompiling a package that normally comes with Slackware,
check the Slackware source directory for that package for the
.SlackBuild file.  This is the build script Slackware uses to build
that package.  You can look at it to find out how to do the appropriate
'make install', or (better) you can modify the script for your needs
(change configuration options, etc) and use it to build your new
package.

>From the slackware 9.1 mysql.SlackBuild
(source/ap/mysql/mysql.SlackBuild on the source CD, or in any Slackware
9.1 mirror), the proper 'make install' for mysql is:

make install DESTDIR=<your target directory>

Ben

-- 
Ben Coleman oloryn at benshome.net      | The attempt to legislatively
http://oloryn.home.mindspring.com/   | micromanage equality results, at
Amateur Radio NJ8J                   | best, in equal misery for all.