[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
slackware:slackbuild_scripts [2012/08/22 11:04 (UTC)] – [Creating SlackBuild scripts] vharishankarslackware:slackbuild_scripts [2012/08/22 11:09 (UTC)] – [Overview] vharishankar
Line 8: Line 8:
  
   - Uncompress the source archive (usually .tar.gz or .tar.bz2 file) into a "work directory."   - Uncompress the source archive (usually .tar.gz or .tar.bz2 file) into a "work directory."
 +  - Create a ''slack-desc'' file, with the description of the software in the correct format.
   - Configure the source, and apply patches if needed.   - Configure the source, and apply patches if needed.
   - Compile/build the source and generate the binaries.   - Compile/build the source and generate the binaries.
Line 15: Line 16:
  
 While the above steps can be done by hand, the process is tedious, sometimes complex, and involves typing in a lot of commands. Automating the process by a shell script allows the user to share the process with the community at large. It also makes sense to use and modify existing SlackBuild scripts for upgrading the same program to a newer version. While the above steps can be done by hand, the process is tedious, sometimes complex, and involves typing in a lot of commands. Automating the process by a shell script allows the user to share the process with the community at large. It also makes sense to use and modify existing SlackBuild scripts for upgrading the same program to a newer version.
- 
 ===== Creating SlackBuild scripts ===== ===== Creating SlackBuild scripts =====
  
 slackware:slackbuild_scripts ()