Hello and welcome Arioco,
it's good that you want to contribute packages and Dave is a great guide.
Other pages you might want to read are:http://forum.vectorlinux.com/index.php?topic=1701.0http://forum.vectorlinux.com/index.php?topic=1380.0http://forum.vectorlinux.com/index.php?topic=8604.0
As a beginner packager, I found the tutorials/how-tos very confusing and spent a long time working out exactly what to do. I wrote a quick guide for myself, summarising the process. You are welcome to use it.
Packaging for Vector Linux 6.0 - A Twelve Step Programme
1. Ensure your environment is a clean install of VL std with no added programs except dependencies for the package you are making.
2. Create a user with your packaging username and log in as that user
3. Download the source file to your empty packaging directory
4. Run sbbuilder in the packaging directory (to make a SlackBuild file and directory structure)
5. Copy the source file into the correct part of the directory tree (/src)
6. Edit the blank slack-desc area of the SlackBuild
7. Save the SlackBuild and make it executable
8. As root user, build the package by running the SlackBuild script.
9. Check the error log. If there are errors, correct them, delete the flawed files then return to 8. Also check through the directory structure of the package (I used mc) making sure everything is tidy with no doubling up. (Have a look at some of the installed packages in the /home/ftp/ (as su) on one of your user machines, to see how others have packaged.)
10. Install (as root) when there are no errors
11. Test the program as a user and if there are no problems:
12. Submit the package, the SlackBuild, slack-desc, and slack-required to ... if there are no problems.
Initially you will have to PM JohnB316 and he will guide you through making an ssh key and setting up an account on the OSL server. You will then see the VL Packagers Board on VL forum's home page. Have a look at how other packagers inform the repo maintainers that they have uploaded a package.
John will tell you how to upload the package. I used gFTP. Then start a new thread on the Packagers board with the package name and the slack-desc and slack-required.
When you upload use this form (pretty much as it comes after running the SlackBuild script):
How I packaged pmplib-0.14 for VL6.0
2. As user (no2thesame):
3. Download pmplib-0.14.tar.gz
mv pmplib-0.14.tar.gz /home/no2thesame/Packaging
sbbuilder --package=pmplib --version=0.14 --link=http://pmplib.sourceforge.net/
cp pmplib-0.14.tar.gz pmplib/0.14/src/
Edit the slack-desc area of as follows:
$NAME: $NAME (create and maintain the music database on various MP3 players)
$NAME: allows tracks to be browsed by artist, album, genre, etc., rather than
$NAME: by directory structure.
$NAME: Supports: iRiver H100, H300, H10 MTP and H10, H10Jr, U10, E10 (UMS);
$NAME: MEDION MDJuke220, MDJuke 440; and Samsung YH-820, YH-920, and YH-925
$NAME: MSI MEGA PLAYER 540
$NAME: Supports: MP3, Ogg Vorbis, WMA, WAV Not supported: m4a
$NAME: License: The GNU General Public License (GPL)Version 2, June 1991
$NAME: Authors: Naoaki Okazaki, Martin Ellis
$NAME: Website: http://pmplib.sourceforge.net
chmod 777 pmplib.SlackBuild
./pmplib.SlackBuild 2>&1 | tee build-pmplib.log
Read error log and if OK, check for pmplib-0.14-i586-1vl60.tlz (the package), slack-desc, and slack-required with.
There was duplication with the same files (README, COPYING etc) in both /usr/doc and /usr/share/doc
(After only trying to package 3 programs (only one successful), I can see that each is very different. Obviously the programmers make their source files in very different ways, meaning that the SlackBuild has to be worked over pretty well.)
so I included this in the SlackBuild (copying the other lines already there)
if [ -d $PKG/usr/share ] ; then
rm -rf $PKG/usr/share
If there are problems, uninstall with:
11. Tested and worked OK on two different machines.
Submitted in this form:
pmplib-0.14-i586-1vl60.tlz slack-desc slack-required
And started a new thread on the VL Packagers Board entitled
with slack-desc and slack-required as code.