It is just a warning that your man pages aren't compressed, thereby wasting a little bit of disk space. No real worry (but if you ever write a Slackbuild, you should go the extra mile and gzip your man pages).

You made the correct choice.

Thank you very much! Now that I overcame my biggest obstacle, slackware is defiantly going to be my main desktop distribution. I was still testing around to see if it was for me or not. Looks like I'll go subscribe to the Slackware CD/DVD now.:)

Switch7: You have ommited one important thing - in the name of slackware package, You should set info about arch, to which is the package designed.
The name of package should be made with this schema: packagename-version-arch-build.txz
Name and version can contain multiple "-" signs, but two last sections must be only alphanumeric signs without extra "-" signs.

Regards :)

libtorrent-0.12.5-x86_64-1.txz
libsigc++-2.2.4.2-x86_64-1.txz
rtorrent-0.8.5-x86_64-1.txz

Something like this?

I seen different numbers in the build number. Instead of -1, I seen something like -29 (ex: libtorrent-0.12.5-x86_64-29.txz) but that's only when the package is a bundle and I wouldn't need anything other than -1 for normal packages?

This is not completely true. The name may contain dashes (the "-" characters) but the version must not have any dashes! So, if a source package has a version of "1.2.3-4" your package version must be changed to something like "1.2.3_4" - Slackware usually replaces dashes in a VERSION with underscores.

Perhaps you should read http://www.slackwiki.org/Writing_A_SlackBuild_Script

Eric

Thank you. I never had any idea this was supposed to be the official way it's used in slackware. I always thought slackbuilds was just third party packages. I'll defiantly take a look here.

Well, the slackbuild scripts are the official way to produce official packages ;) Slackbuilds save time for future releases, and rebuilds.

And I appologize for my mistake. Eric has always right ;) Only name of the package can contain multiple dashes.