Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
slackbuilds [2015/05/15 10:41]
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"​ ''​   -Run the SlackBuild, as root: ''​su -c "​./​foo.SlackBuild"​ ''​
   -Install the resulting package: ''​su -c "​installpkg /​tmp/​foo_sbo.tgz"​ ''​   -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 126: Line 163:
 A typical use for this would be, for instance, when installing ''​Inkscape''​. Doing a search for "​inkscape"​ reveals that there is a SlackBuild available, but that it depends on a number of other packages such as ''​pangomm'',​ ''​cairomm'',​ and others. Adding ''​Inkscape''​ to the queue allows the user to then go seek out SlackBuild packages for its dependencies and either install them one by one, or add them to the queue as well. If they are added to the queue, then the queue exists, essentially,​ in reverse order (that is, the dependencies need to be compiled before the application that depends upon them). Fix this in the ''​Sort Queue''​ submenu by either manually rearranging the order of the queue, or have ''​sbopkg''​ reverse it for you. A simple reversal of the queue sometimes does work, but it may be insufficient since a dependency of one application may have its own dependencies which may require manual re-ordering to do sub-sorts in the queue. ​ A typical use for this would be, for instance, when installing ''​Inkscape''​. Doing a search for "​inkscape"​ reveals that there is a SlackBuild available, but that it depends on a number of other packages such as ''​pangomm'',​ ''​cairomm'',​ and others. Adding ''​Inkscape''​ to the queue allows the user to then go seek out SlackBuild packages for its dependencies and either install them one by one, or add them to the queue as well. If they are added to the queue, then the queue exists, essentially,​ in reverse order (that is, the dependencies need to be compiled before the application that depends upon them). Fix this in the ''​Sort Queue''​ submenu by either manually rearranging the order of the queue, or have ''​sbopkg''​ reverse it for you. A simple reversal of the queue sometimes does work, but it may be insufficient since a dependency of one application may have its own dependencies which may require manual re-ordering to do sub-sorts in the queue. ​
  
-<​WRAP ​info>+<​WRAP ​tip>
 As is usually the case with Slackware, there is nothing being done here that you cannot do yourself. If you find the ''​sbopkg''​ interface limiting, you may create queue files manually in any text editor and load the file into ''​sbopkg''​. As is usually the case with Slackware, there is nothing being done here that you cannot do yourself. If you find the ''​sbopkg''​ interface limiting, you may create queue files manually in any text editor and load the file into ''​sbopkg''​.
 </​WRAP>​ </​WRAP>​
Line 176: Line 213:
 ''​Sport'',​ the "​Slackware Port" system, is Slackermedia'​s shell frontend to [[http://​slackbuilds.org]]. It is meant to be simpler and less interactive than ''​sbopkg'',​ ''​Sport'',​ the "​Slackware Port" system, is Slackermedia'​s shell frontend to [[http://​slackbuilds.org]]. It is meant to be simpler and less interactive than ''​sbopkg'',​
 and it instead emulates the BSD ports system, or the ''​emerge''​ system from Gentoo. and it instead emulates the BSD ports system, or the ''​emerge''​ system from Gentoo.
 +
 +[{{ 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. 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.
  
-<​WRAP ​info>+<​WRAP ​tip>
 Since the most prolific and uniform collection of SlackBuilds is [[http://​slackbuilds.org]],​ and since Slackermedia is so heavily reliant upon SlackBuilds.org,​ ''​sport''​ is largely modeled after the structure of SBo, although it is not restricted to it and technically will work with any collection of builds (such as your own personal collection of modified builds, or those of trusted associates). Since the most prolific and uniform collection of SlackBuilds is [[http://​slackbuilds.org]],​ and since Slackermedia is so heavily reliant upon SlackBuilds.org,​ ''​sport''​ is largely modeled after the structure of SBo, although it is not restricted to it and technically will work with any collection of builds (such as your own personal collection of modified builds, or those of trusted associates).
 </​WRAP>​ </​WRAP>​
Line 245: Line 284:
 The search function of ''​sport''​ performs a fuzzy search on any term you provide. A search for "​foo"​ therefore returns the category and packages names for both the stand-alone ''​foo''​ and, in this example, the ''​emacs-foo''​. It also returns a string in which "​foo"​ appears; as in ''​kfooplayer''​. The search function of ''​sport''​ performs a fuzzy search on any term you provide. A search for "​foo"​ therefore returns the category and packages names for both the stand-alone ''​foo''​ and, in this example, the ''​emacs-foo''​. It also returns a string in which "​foo"​ appears; as in ''​kfooplayer''​.
  
-<​WRAP ​info>+<​WRAP ​tip>
 If you only want to browse through your SlackBuilds tree without having to think up search terms, cd into ''/​usr/​ports''​ (or whatever you have set ''​SBOPATH''​ to) and browse its contents. If you only want to browse through your SlackBuilds tree without having to think up search terms, cd into ''/​usr/​ports''​ (or whatever you have set ''​SBOPATH''​ to) and browse its contents.
 </​WRAP>​ </​WRAP>​
Line 283: Line 322:
 happens to find lying around. happens to find lying around.
  
-<​WRAP ​info>+<​WRAP ​important>
 //Resolving dependencies//​ may sound mysterious but all it means is that you will have to install some additional system libraries or smaller applications before you install the application you are trying to obtain. To resolve the dependencies of ''​foo'',​ you would take note of the libraries it requires (''​bar''​ and ''​baz''​) and then use ''​sport''​ to install each one before then installing ''​foo''​ itself. //Resolving dependencies//​ may sound mysterious but all it means is that you will have to install some additional system libraries or smaller applications before you install the application you are trying to obtain. To resolve the dependencies of ''​foo'',​ you would take note of the libraries it requires (''​bar''​ and ''​baz''​) and then use ''​sport''​ to install each one before then installing ''​foo''​ itself.
 </​WRAP>​ </​WRAP>​
Line 367: 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>​