Where can I find more information about making Slack packages? I bought
the Slackware Essentials book but there is no much information about that.
I found some howto on the internet but it works for only some programs.
Here's what it says:

-------------start---------------------------
../configure --prefix=/usr
make
grep -r DESTDIR *

Installing with DESTDIR-support

make DESTDIR=/tmp/slackpack/example-0.1-beta install
Installing without DESTDIR-support

No worries, just put the wanted DESTDIR in front of the prefix, and install like so:

make prefix=/tmp/slackpack/example-0.1-beta/usr install

cd /tmp/slackpack/example-0.1-beta
makepkg example-0.1beta-i386-1.tgz
-----------------end----------------------------

I'd like to know more about making Slack, especialy if there is some
utility for making it (I don't mean about Checkinstall ). I'd like to
make packages for Ralink drivers and kernel modules package.

Thank you.

--
Igor Jagec

On Thu, 07 Apr 2005 13:46:39 +0200, Igor Jagec <igor.jagec@start.wlan>
wrote:

>Where can I find more information about making Slack packages? I bought
>the Slackware Essentials book but there is no much information about that.
>I found some howto on the internet but it works for only some programs.

http://www.linuxpackages.net/howto.p...=Package+Howto
http://linuxtipps.sourceforge.net/sh...tutorial/9.htm
http://www.neowin.net/forum/lofivers...p/t139715.html

I followed the instructions from those pages and successfully created
my own mplayer package.

Dazz

<snipped>

>Thank you.

On 2005-04-07, Igor Jagec <igor.jagec@start.wlan> wrote:
> Where can I find more information about making Slack packages? I bought
> the Slackware Essentials book but there is no much information about that.
> I found some howto on the internet but it works for only some programs.
You can try
http://www.interlude.org.uk/unix/sla...esentation.pdf

for a brief introduction on how things work wrote by Stuart Winter.

> I'd like to know more about making Slack, especialy if there is some
> utility for making it (I don't mean about Checkinstall ). I'd like to
> make packages for Ralink drivers and kernel modules package.

Look at slacktrack (in /extra), it's easy to use and well written.
You can find some nice examples on how to use it and how to make scripts
both in the /source tree or in the official site
http://www.interlude.org.uk/unix/slackware/


Gufo
--
,___, |
(9v9) | As long as the answer is right,
(_^((\ | who cares if the question is wrong?
-^-"-"-\\-^-- |

On Thu, 07 Apr 2005 13:20:15 GMT, gufo-me-@despammed.com wrote:

> You can try
> http://www.interlude.org.uk/unix/sla...esentation.pdf
>
> for a brief introduction on how things work wrote by Stuart Winter.

The original notes for that talk are here:

http://www.interlude.org.uk/unix/sla...SDEM_SLACK.txt

They may be helpful since I tried to keep the slide content to a minimum.

> You can find some nice examples on how to use it and how to make scripts
> both in the /source tree or in the official site
> http://www.interlude.org.uk/unix/slackware/

You should grab the examples from the URL there rather than from slackware/extra
because I updated them recently, but since I have not yet released the newer
version of slacktrack, I haven't asked Pat to update the examples.

Cheers
Stuart.
--
www.armedslack.org
| "Washing machines live longer with Calgon"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, Igor Jagec dared to utter,
> Where can I find more information about making Slack packages?

You came to the right place. :^)

> I'd like to know more about making Slack, especialy if there is some
> utility for making it (I don't mean about Checkinstall ). I'd like to
> make packages for Ralink drivers and kernel modules package.

Well, when you wish to create a Slackware package, the first thing to
do is see if most of the work has already been done for you. If the
utility you wish to package is already a part of Slackware, look in the
/source directory and find it. In there, you may find a
$UTILITY.SlackBuild script. Just editing the version, arch, and build
for this shell script will give you an executable script that will
build one for you. If your app is not included in Slackware, google
around for an applicable SlackBuild. Also, check out SlackBuild
Central[0] which is operated by this newsgroup's very own George
Georgakis.

Now if you can't find a SlackBuild script, you have a few options.

1) Make one! SlackBuild scripts aren't that hard, and since you're
going to make a package anyway, why not make the script so updating
will be easier next time? Better yet, share the script with the rest
of the world on your own site, or preferably SlackBuild Central.
2) Create one using makepkg. The instructions you received are typical
of makepkg. The idea is to build a package normally, but at the "make
install" step, add an environment variable DESTDIR. DESTDIR is the
directory to which you want the package to be installed. You can
create something like /tmp/pkg, and when you install to that directory,
you'll have something you can just run makepkg on you're good to go.
Beware: some programs just don't honor DESTDIR at all, and some only
partially honor it, resulting in a broken package.
3) Use a third-party utility like checkinstall instead of the "make
install" phase. checkinstall and tools like it watch for calls to the
kernel for writing files and creating directories and intersept them.
They then take the files and directories that were to be written and
recreate them inside a slackware package. Beware: some of these tools
are sub-optimal. It's always preferred to use makepkg when possible,
particularly if you are going to be sharing these packages with the
world.

[0] http://slackpack.tripleg.net.au/

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCVUmmvgVcFKpJf4gRAk/6AKCQptVI2OW9raoBxxmwx6wsF3cjxQCfVQVo
UeA+ew6IIpOcd5K2aS4ufhQ=
=ehwy
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, Stuart Winter dared to utter,
>> http://www.interlude.org.uk/unix/sla...esentation.pdf
> http://www.interlude.org.uk/unix/sla...SDEM_SLACK.txt

A wonderful resource, read together. To the OP, Stuart is the
"Slackware Packaging Expert", so he's the guy to listen to most on this
issue. ;-)

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCVYquvgVcFKpJf4gRAkMBAKCwLXEhqXY9voaXKJG/XIm0PmqbUACfS9dR
YotZrAHOzfUlfh0bhYM+cEc=
=7TeG
-----END PGP SIGNATURE-----

On Thu, 07 Apr 2005 22:24:48 +1000, Dazz wrote:

> http://www.linuxpackages.net/howto.p...=Package+Howto
> http://linuxtipps.sourceforge.net/sh...tutorial/9.htm
> http://www.neowin.net/forum/lofivers...p/t139715.html

Thanks. I'll go see it as soon as I go online.

> I followed the instructions from those pages and successfully created
> my own mplayer package.

I forgot to say, following the instructions I mentioned I made 7 packages
But the problem was that I couldn't make packages from all the sources
that way and I don't know why. Hope I'll find the answers in those links.

Thanks again.

--
Igor Jagec

On Thu, 07 Apr 2005 14:53:18 +0000, Stuart Winter wrote:

> http://www.interlude.org.uk/unix/sla...SDEM_SLACK.txt
> They may be helpful since I tried to keep the slide content to a minimum.

Thanks. I'll go see it as soon as I go online

>> You can find some nice examples on how to use it and how to make scripts
>> both in the /source tree or in the official site
>> http://www.interlude.org.uk/unix/slackware/
> You should grab the examples from the URL there rather than from slackware/extra
> because I updated them recently, but since I have not yet released the newer
> version of slacktrack, I haven't asked Pat to update the examples.

Hmmm, I thought Slacktrack is only for building sources I got with
distribution:

-----------------------------------------------------------------
DESCRIPTION
slacktrack is a packaging tool to build replicar Slackware
packages from the official .build scripts available in the
distribution source tree. slacktrack has many features
available to eliminate the majority of the manual element
involved with producing packages from these scripts.
slacktrack uses the standard Slackware makepkg program to
produce the resulting packages.
----------------------------------------------------------------

I got it all wrong I suppose. Never mind, I'll go see it all as soon as I
go online. Thank you all guys.

--
Igor Jagec

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 07 Apr 2005 13:46:39 +0200, Igor Jagec wrote:
> Where can I find more information about making Slack packages? I bought
> the Slackware Essentials book but there is no much information about that.
> I found some howto on the internet but it works for only some programs.
> Here's what it says:
>
> -------------start---------------------------
> ./configure --prefix=/usr
> make
> grep -r DESTDIR *
>
> Installing with DESTDIR-support
>
Ok. This shows that the Makefile likely supports DESTDIR.

> make DESTDIR=/tmp/slackpack/example-0.1-beta install

Here it may have worked differently if you had put the two commands
on separate lines. I assume DESTDIR= is being used by make but not
install.

Try it as make; DESTDIR=/tmp/slackpack/example-0.1-beta install


> Installing without DESTDIR-support
>
> No worries, just put the wanted DESTDIR in front of the prefix, and install like so:
>
> make prefix=/tmp/slackpack/example-0.1-beta/usr install

If my assumption were correct, which it may not be, then with that
command the program may be built with hardcoded paths to that
prefix= location. You want to run make with the prefix= of where you
want the final program to be installed to, and you want to run
install with DESTDIR= (or prefix=) with the temporary location you
want to build the package from.

>
> cd /tmp/slackpack/example-0.1-beta
> makepkg example-0.1beta-i386-1.tgz
> -----------------end----------------------------
>
> I'd like to know more about making Slack, especialy if there is some
> utility for making it (I don't mean about Checkinstall ). I'd like to
> make packages for Ralink drivers and kernel modules package.
>
The others pointed out some excellent resources. The Checkinstall
program in /extra is also very nice.

Brad


-----BEGIN PGP SIGNATURE-----

iD8DBQFCVkF0kDp4KjYna1ARAoJXAJ9YBk52b0wZwFSeFjZThj ADOmE9EACfcMma
e1EVOY86OhJyYc7/HCeY36Q=
=+eOR
-----END PGP SIGNATURE-----

On Fri, 08 Apr 2005 00:42:32 +0200, igor.jagec@start.wlan wrote:

> Hmmm, I thought Slacktrack is only for building sources I got with
> distribution:
>
> -----------------------------------------------------------------
> DESCRIPTION
> slacktrack is a packaging tool to build replicar Slackware
> packages from the official .build scripts available in the
> distribution source tree. slacktrack has many features
> available to eliminate the majority of the manual element
> involved with producing packages from these scripts.
> slacktrack uses the standard Slackware makepkg program to
> produce the resulting packages.
> ----------------------------------------------------------------

I've never made it 100% clear that it can be used to build packages
from any other build scripts (although if one were to look at
Slackware's .build scripts it would become quickly apparent that
this was possible; but then if you never looked because the description
never advertised it..). Now I know why I don't work in marketing ;-)

Perhaps I will change the slack-desc and other descriptions for the
next release.

--
www.armedslack.org
| "Washing machines live longer with Calgon"