Hi!
Fist of all, welcome to the Slacky.eu community!
One thing before i describe you everything: please write an introduction here:
viewforum.php?f=53
Ok, let's start.
These are our guidelines: unfortunately for you, they are in italian.
http://www.slacky.eu/slacky/Linee_guida ... kware_14.1
I'm going to try to explain you
1) You MUST use a full and clean install Slackware. A chrooted Slackware installation works fine too.
(Here a script that can automate the process.
http://www.slacky.eu/slacky/Slackware_C ... utoBuilder)
A x64 Slackware host can be used for both x86 and x64 Slackware chroot installations.
2) This is the standard template: you have to delete all unnecessary commented lines, except the licence at the head of the script.
http://www.slacky.eu/wikislack/upload/4 ... emplate.sh
In our guidelines you can find templates for cmake and other types of compilation, they are easy to find.
3) You must install requiredbuilder, that create automatically the slack-required file (used by our tool, slackyd, for dependencies checking). You can find it in our repository.
4) The doinst.sh file, that is the post-install script, is optional. If you require it, this is the template.
http://www.slacky.eu/wikislack/upload/3 ... i.template
5) The slack-desc file (that is MANDATORY) can be found on Slackbuilds.org, on previous versions inside our repository or you can use this bash script to automate this.
http://www.slacky.eu/slacky/Crea_file_slack-desc
Most of the cases, you have only to edit the first part of the script:
- Name of package
- Number version
- Build version: if there is a previous version, even on an older repository (ex: 13.3 or 14.0 repository) and same version number you have to increase.
If version number is different, reset it to "1".
- Tag: don't touch it, on Slacky.eu we use "sl".
- Architecture: x86_64 if target is a x64 package.
- Source url
Codice: Seleziona tutto
SOURCE="http://downloads.sourceforge.net/project/......./${PKGNAME}-${VERSION}/${PKGNAME}-${VERSION}.tar.gz"
- Tarball and directory name: if tarball have a non-standard name, write it. If not, leave it blank.
Example: standard template is name-version.tar.(bz2,gz,xz). If is different, type on it a name for the tarball (usually we retype standard name: $PKGNAME-$VERSION.tar.(bz2.gz.xz) )
Same speech for the DIR variable, that is about main directory inside the tarball.
- Documents: if there are some additional documents, write their name here.
Codice: Seleziona tutto
DOCS="AUTHORS COPYING INSTALL TODO TROUBLESHOOTING docs/ ..."
- Other files: same as documents, but if they are other files (like additional patches)
I think you know how to launch a SlackBuild compilation.

The directory tree must be like this, after a compilation:
Codice: Seleziona tutto
name
-version
--package.txz
--src
---name.SlackBuild (don't forget the upper case)
---slack-desc
---slack-required
---doinst.sh (optional)
---patches (optional)
DON'T keep the source tarball, except if it is not downloadable anywhere.
When all is done, package the directory tree inside a tarball and send it to our admin, Loris:
slacky@slacky.it
Ok, i think that's all.
Excuse me for my bad english and enjoy our packager' section and our forum
