Differences

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

--- slackbuilds [2015/05/16 09:59]
slackermedia
+++ slackbuilds [2021/06/03 19:48] (current)
@@ Line 1: / Line 1: @@
-[[{arrowp.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;left:0;}pkg|]]
-[[{arrown.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;margin-left:2.5em;}dep|]]
@@ Line 30: / Line 28: @@
   -Run the SlackBuild, as root: ''su -c "./foo.SlackBuild" ''
   -Install the resulting package: ''su -c "installpkg /tmp/foo_sbo.tgz" ''
+====Common SlackBuild Mods====
+The great thing about a SlackBuild script is that it can be modified by you, the user. SlackBuilds have several properties that are set by the script's author to default values, but which can be over-ridden by the user.
+It is a convention is SlackBuild scripts from SlackBuilds.org that any value that can be defined by the user is written in CAPS. In theory, you can see most of these values in a script use ''egrep'':
+<code>
+$ egrep '[A-Z]+=' audacity.SlackBuild
+</code>
+In practise, there are certain strings that you will modify more often than others.
+{{anchor:versionmod}}
+**VERSION**
+<WRAP indent>
+If a site offers a SlackBuild for ''foo-1.0'' but you know that ''foo-2.0'' has just been released, update the VERSION string:
+<code>
+$ VERSION=2.0 ./foo.SlackBuild
+</code>
+</WRAP>
+{{anchor:optionmod}}
+**Options**
+<WRAP indent>
+Sometimes a SlackBuild author offers the user a choice in what should or should not be included in a build. For example, if a plugin is offered as both an LV2 and a VST, the author might provide the option to build both by default, with manual over-rides to drop one or the other. This is usually communicated to you in the README file.
+<code>
+$ VST=no ./foo.SlackBuild
+</code>
+</WRAP>
@@ Line 177: / Line 214: @@
 and it instead emulates the BSD ports system, or the ''emerge'' system from Gentoo.
-{ sport.png }
+[{{ sport.png |The sport interface.}}]
 Like other Slackware package installation applications, ''sport'' is not a package manager as you would find in [[http://debian.org|Debian]] or [[http://redhat.com|Red Hat]]. However, it does help you search through your collection of SlackBuilds, read relevant files about each SlackBuild, and then execute the build and install processes.
@@ Line 369: / Line 406: @@
-[[{arrown.png|border:0;background:none;width:0;display:inline-block;float:right;}dep|]][[{arrowp.png|border:0;background:none;width:0;float:right;}pkg|]]
+<WRAP centeralign>
+<wrap fa>[[pkg|R]]</wrap> <wrap fa>[[start|S]]</wrap> <wrap fa>[[dep|Q]]</wrap>
+</WRAP>