If you are taking requests ( ) there is certainly a need for "how to package"... maybe you could tackle the "advanced" help

please keep at it!

- Howard

Hey Howard, thanks for the request. Packaging is a tough one, I think it would have to be a series of tutorials. I'm just starting to study the topic but what works on some source code, just doesn't work on others and I'm not quit sure how to identify the difference yet.

This tutorial show how to create a .tgz for a program called sudokuki using sbbuilder. It should be a good starting point for series of tutorials on 'how to package'. It should work for other programs where ./configure, make, make install is the chosen build method.Also I don't mind editing my mistakes and I am new at this so If any of the more experienced have some pointers I'm all ears.

@kidd, thank you! I think an edit may be a good idea, seeing that I missed out on how the sbbuilder script automates the inclusion of the package $NAME. I'll be playing with different script edits over the weekend, maybe then.

Here's another. This one for pdfedit. This screencast kind of highlights how the .SlackBuild script generated by sbbuilder often times needs to be edited to suit the application. From what I understand the type of edit here is common enough that a new packager will benefit knowing what to look for and how to adapt the script.

stretchedthin: I just watched one of your new videos about the terminal. (Changing directories, creating, moving, and removing files) (How did you do the red circles by the way?) Like all the other videos it was very well done and would be very useful to a newbie but there were a couple things I noticed about it. I'm not sure if it was intentional but I noticed that the mouse movements in the video were kind of rough. Also, the resolution/screensize was set a little low. It was kind of hard to read the words and commands in the terminal. One interesting piece to information that you may want to put in the video in the part about the "ls" command is that you can also use "dir" to list directory contents just like in dos. People coming from Windows might like that feature. You might also want to check spelling and grammer in all of your callouts. It's usually not a big deal but once or twice I saw a spelling error that could confuse a newbie. (I think it was part of a command or something) One last thing: on the home page of opensourcebistro.com, in the section where it mentions that you can submit your own tutorials, it says "Have Your created a tutorial..." instead of "Have you created a tutorial..." Overall, I like the site a lot. I'll keep watching for more videos and if/when I get VL 6.0 I might be able to help make some tutorials. (I have 5.9.1 SOHO right now and am experimenting with Wink )

Thanks Daniel; Thanks for being a second set of eyes for me. I tend to move on to the next project before polishing the last. I would really welcome the contributions when you get a chance. If you like soho you could do soho, I'd just make a page for it.

You're welcome. I might send in some tutorials after I learn Wink a little more. BTW, how did you do the little red circles on the video about the terminal that I mentioned? Also, the video about the "init" command and runlevels. Have the runlevels changed between 5.9 and 6.0? In 5.9, runlevels are 2, 3, 4, and 5. There is no 1 or 6. Can you please clarify this?

Also, the video about the "init" command and runlevels. Have the runlevels changed between 5.9 and 6.0? In 5.9, runlevels are 2, 3, 4, and 5. There is no 1 or 6. Can you please clarify this?

I based that tutorial on slackware runlevel infomation I found. The init numbers do not match up with the runlevels as described in vasm I found. 'init 1' in the terminal brought up a single user text mode, init 3 brings up multiuser text mode, init 6 is not a runlevel at all it just restarts the computer and init 0 shuts it off.

I have also re-done the screencast for the pdfedit build. This one now shows how to get the .desktop file and .png icon included in the build.http://www.opensourcebistro.com/Tutorial/VL60/VLpackaging/pdfedit-sbbuild.htmThe method shown in the tutorial works and is straightforward but there is probably a more recognized method for including these files, could someone let me know what it is?

Also, if someone would be OK with me pm'ing or emailing them directly with questions, I have some on building for the other types in sbbuilder, ie. --type=python.

Finally, in doing this I now have Grisbi, Sodokuki, and PDFedit ready to go as .tlz's. How do I submit them?

I liked the pdfedit tutorial very much. It's nice how you go increasing difficulty little by little.

I have some comments though . Again, no need to rebuild anything, just think about that for the next ones.

When replacing the $CWD/$NAME.png and $CWD/$NAME.desktop , I find to be a better solution to move both png and .desktop to the place where the slackbuild is. This way, You won't need to modify paths, and when you upload the package, you'll be uploading a complete black box everyone will be able to run and get a package (We try to keep that possible to be able to automate packaging for vl64) .

Thanks again, kidd for your input.I have edited the tutorials and included the changes you suggested.I now have three that will make up a 6 part series on packaging for a --type=normal SBbuilder, build.

Just having a go at packaging myself so I thought I'd take a look at one of your tutorials.

Have spotted a few minor typo's in Manual build part 1.1:

-Second balloon has 'manuel' instead of 'manual'.-'I've isolated download of Grisbi.tar.gz' (in the file viewer it's .tar.bz2)-'right click and choose 'extract' then 'extact'' (missing 'r' in extract)-'./configure -prefix=/user' (it should be /usr not /user and shouldn't it be --prefix=/usr)-Have you missed a cd install prior to the requiredbuilder step?-'Then -c n lets makepg (missing k ) know that is ( is instead of it ) must not change permissions

Once again a great tutorial that should help those considering packaging take their first steps.

I'll have a look through that one again and clean it up a bit, once I get back home. Having a bit of a family outing this weekend but I should be able to clean up the screencast shortly after I get back home.

Make sure to try out the sbbuilder screencasts as well.

It sure would be a validation of these tutorials and of kidd and rbistolfi's SBbuilder if we see a greater number of people contributing packages. Thanks again.

I've got one more to add to the series. Kidd really helped with this one (read as...told me what to do and I made a screencast of it ). If covers a lot of difficult situations that could be helpful with any build.