You can download a package, and explode it in your build environment, so that you can look at the scripts in the package. For example, the screen shot below shows part of the script for the package"FLDIGI"Thanks for the guidance and welcome VPKS.
I read the man page for makepkg. From that I understand that there are 3 types of scripts.
Will I have to run a script in order to be able to make a pkg?
Do I need to write the script myself?
That is a very nice blog. Thanks for the info, mate! I pasted it into a document for further study.Take a look at the man page for 'makepkg'. It is brief, but it is the command to make the Slackware package. If that is too brief of an explanation, then look at http://karellen.blogspot.com/2011/12/slackware-package-management.html, scroll down to the section of Creating a package:Basic.
This is going to take some time for me to understand.You can download a package, and explode it in your build environment, so that you can look at the scripts in the package. For example, the screen shot below shows part of the script for the package"FLDIGI"View attachment 4066
The wiki for this would be https://www.slackwiki.com/Writing_A_SlackBuild_Script. It will take a while to understand it, I don't fully myself as yet, so take your time with it, and remember to have fun!
well my current thinking is this: brush up on bash ,so i have half a clue what stuff in slackbuild means , maybe cheat and just use alien slackbuild tool https://alien.slackbook.org/AST/ if i really feel gung ho have a read of https://www.slackwiki.com/Writing_A_SlackBuild_Script probably the first step would be to think of the most simple basic package that could possibly be built - i'm open to suggestions . Then of course open up a few Slackbuilds from slackbuilds.org & see if there is any pattern to them.Hi:
I do pretty will at keeping Slackware up to date and can install most things however; I would like to learn how to make my own packages.
Anyone good at this or could post me a link where I could learn how?