Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Arioco]

Hi everybody, I had an old PII 400Mhz, 256Mb RAM, abandoned somewhere in my house being of no use so I decided to Install VL6 Light on it and use it to Build Packages, it's not like I have a lot of time or experience, but I think I can Build small and easy to compile packages at first and learn, maybe I can become a full fledged packager. I've Build some packages, but I want somebody to tell me if i did it right, an tell what to do to share them.

until a few weeks Ago I was using VL 5.9.1 SOHO in my Desktop PC, I use a GPRS modem for my internet connection, in a SOHO edition I had no problem, Kppp Handled it well, but now in VL6 STD I find that chestnut-dialer uses a max speed of 115200 Bauds (at least I couldn't find a way to use more than that) that's eight times slower than the max speed of my modem, and you can't minimize chestnut-dialer to tray. I didn't want to install kdenetwork package just for the dialer so I decided to Build wvstreams and wvdial.

I also packaged mupen64plus and zsnes to install them in my little sister's PC (she is soo fan of The Legend Of Zelda: The Ocarine of time)

so those would be my first contribution, I don't know if somebody want to check the scritps or something, I hope somebody tell me what to do.

I'll be seeing you, take care

[kc1di]

There is a good Article in the forum that describes how to package for VL.  It's at

ftp://64.50.238.52/.1/vectorlinux/docs/packaging/index.html

It's a little dated but still full of good advice.  One of the most import aspects is that you need a Clean machine (that is without a lot of extra stuff on it. or a CHroot jail)  You may want to P.M. Toothandnail (he is one of the repro managers and have him check your packages. )  He can then give you instructions on getting them into the repositories if they pass muster. 

Their is a good package building script in the Repositories call sbbuilder also. You will want to use that to make your build scripts. 

Let us know if you have further questions.

Dave

[no2thesame]

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.0
http://forum.vectorlinux.com/index.php?topic=1380.0
http://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):
<contrib-name>
          |
     VL6.0
          |
     <packagename>
              |
           <version>
             package files
        
                  |
                src
               source files

----------------------       

Example:
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

   cd /home/no2thesame/Packaging
4.
   sbbuilder --package=pmplib --version=0.14 --link=http://pmplib.sourceforge.net/
5.
   cp pmplib-0.14.tar.gz pmplib/0.14/src/

   cd pmplib/0.14/src/
6.
   medit pmplib.SlackBuild

Edit the slack-desc area of as follows:

   $SHIM|-----handy-ruler------------------------------------------------------|
   $NAME: $NAME (create and maintain the music database on various MP3 players)
   $NAME:
   $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

7.
   chmod 777 pmplib.SlackBuild

8.
   su
   ./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.
   
   cd ../
   ls
   
9.
   less build-pmplib.log
   mc pmplib-0.14-i586-1vl60.tlz
   
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
fi   
10.
   su
   installpkg pmplib-0.14-i586-1vl60.tlz

If there are problems, uninstall with:

   su
   removepkg pmplib-0.14-i586-1vl60.tlz

11. Tested and worked OK on two different machines.

12.

Submitted in this form:

no2thesame
   |
   VL6.0
   |
   pmplib
      |
      0.14
      pmplib-0.14-i586-1vl60.tlz  slack-desc  slack-required
      |
      src
      pmplib-0.14.tar.gz  pmplib.SlackBuild*

And started a new thread on the VL Packagers Board entitled
pmplib-0.14
with slack-desc and slack-required as code.
------------

[Arioco]

hi, thanks for the information, i will take some days to read the documentation and maybe i submit something soon

[Arioco]

hi again

I have a new Question, I've build a package for tilda but before that I built a package for it's dependency libconfuse now that tilda package has been built that dependency is not listed in the slack-required file, so just to try I've installed tilda without libconfuse in my sister's PC and it is working without problem and not a single error output if I run it from the terminal.

is it possible that the dependecy is just necessary to compile it and not to install and run it?

if it isn't needed to run the package. Should I upload libconfuse to the repo?

I've also tried to compile it with no libconfuse installed but it didn't compile because the missing dependency. (Is because of that it is called libconfuse? lol)

[stretchedthin]

Hi Arioco;

Here is the simplest solution I can offer you.

Use SBbuilder to generate your SlackBuild script.

In the slackbuild script you will see a line like this...

ADDRB=${ADDRB:-""} #Add deps that need to be added to the slack-required file here

Change that line to read...

ADDRB=${ADDRB:-"libconfuse >= x.x.xx-i586-1vl60"} #Add deps that need to be added to the slack-required file here

This will force the dependency into slack-required and you are back in business.

[Arioco]

Thanks stretchedthin

that was  a quick answer I,ve done like you said and now it's all fine.

[stretchedthin]

I had the same problem two days ago and rbistofi helped me out.  He and kidd, really thought of most everything with that SBbuilder script.