Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
pkg [2015/07/08 01:55] slackermedia [Distributors of Slack Packages] |
pkg [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;}linuxaudio|]] | ||
| - | |||
| - | [[{arrown.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;margin-left:2.5em;}slackbuilds|]] | ||
| - | |||
| - | |||
| ====== Understanding How Applications are Managed ====== | ====== Understanding How Applications are Managed ====== | ||
| Line 190: | Line 185: | ||
| system. | system. | ||
| + | {{anchor:repo}} | ||
| ==== Distributors of Slack Packages ==== | ==== Distributors of Slack Packages ==== | ||
| Line 268: | Line 264: | ||
| * It ensures the availability of applications to all users on any GNU, Linux, or unix-like system; source code is universal in that if an application was written for a GNU Linux system then it will compile and run on any GNU Linux system regardless of distribution. | * It ensures the availability of applications to all users on any GNU, Linux, or unix-like system; source code is universal in that if an application was written for a GNU Linux system then it will compile and run on any GNU Linux system regardless of distribution. | ||
| - | The general process of compiling is in theory simple. Obtaining it is much like obtaining any downloadable software; you go to a website or a code management site (like [[http://sourceforge.net/directory/os:linux/|Sourceforge or [[https://github.com/notklaatu|Github]] or [[https://gitlab.com/u/notklaatu|Gitlab]]) and download the source code of an application. Typically, free software is available in both a work-in-progress ("current" or "nightly") form as well as a packaged "stable" release version. Slackermedia recommends, with few exceptions, downloading the stable version, which indicates that the code has been tested to some degree and that the programmers of the application feel confident enough in the code to package it into a ''.zip'' or ''.tar.gz'' or ''.tar.bz2'' archive, give it an official number and sometimes a release name, and offer it for download to the general non-programmer public. | + | The general process of compiling is in theory simple. Obtaining it is much like obtaining any downloadable software; you go to a website or a code management site (like [[http://sourceforge.net/directory/os:linux/|Sourceforge]] or [[https://github.com/notklaatu|Github]] or [[https://gitlab.com/u/notklaatu|Gitlab]]) and download the source code of an application. Typically, free software is available in both a work-in-progress ("current" or "nightly") form as well as a packaged "stable" release version. Slackermedia recommends, with few exceptions, downloading the stable version, which indicates that the code has been tested to some degree and that the programmers of the application feel confident enough in the code to package it into a ''.zip'' or ''.tar.gz'' or ''.tar.bz2'' archive, give it an official number and sometimes a release name, and offer it for download to the general non-programmer public. |
| Once the code has been downloaded, it is uncompressed, and a series of two or three commands are issued which starts GNU gcc, which compiles the code and then sends the binaries into the system (//viz.// it is "installed"). | Once the code has been downloaded, it is uncompressed, and a series of two or three commands are issued which starts GNU gcc, which compiles the code and then sends the binaries into the system (//viz.// it is "installed"). | ||
| + | {{anchor:compile}} | ||
| ==== How to Compile Software from Source ==== | ==== How to Compile Software from Source ==== | ||
| Line 401: | Line 398: | ||
| Install it with ''installpkg''. A Slackware package can also be used on other Slackware machines, so you may wish to store it somewhere for later use or re-distribution. | Install it with ''installpkg''. A Slackware package can also be used on other Slackware machines, so you may wish to store it somewhere for later use or re-distribution. | ||
| + | </WRAP> | ||
| **Python Distutils** | **Python Distutils** | ||
| + | <WRAP indent> | ||
| ''Distutils'' is the default method for installing Python applications, since it is the distribution tool that ships with Python itself. Generally, it places all configuration and installation actions in a setup.py file. It is, however, highly customisable, so be sure to read any documentation about installation that the developer of the code provides. | ''Distutils'' is the default method for installing Python applications, since it is the distribution tool that ships with Python itself. Generally, it places all configuration and installation actions in a setup.py file. It is, however, highly customisable, so be sure to read any documentation about installation that the developer of the code provides. | ||
| Line 420: | Line 419: | ||
| Install it with ''installpkg'', and of course you can store this Slack package somewhere for later use or for re-distribution, if needed. | Install it with ''installpkg'', and of course you can store this Slack package somewhere for later use or for re-distribution, if needed. | ||
| + | </WRAP> | ||
| There are many more build systems out there, and there is even the remote possibility that entirely custom install commands or no install commands could turn up. In the event of non-standard build systems, you can read the documentation included with the code and attempt a build nevertheless. If you can't figure out how to redirect the install process, you can choose to install without creating a Slack package; theoretically, that will be harder to un-install or update, but it might be a trade-off worth making, depending on the application and how badly you want it. | There are many more build systems out there, and there is even the remote possibility that entirely custom install commands or no install commands could turn up. In the event of non-standard build systems, you can read the documentation included with the code and attempt a build nevertheless. If you can't figure out how to redirect the install process, you can choose to install without creating a Slack package; theoretically, that will be harder to un-install or update, but it might be a trade-off worth making, depending on the application and how badly you want it. | ||
| Line 436: | Line 435: | ||
| Read how to use [[slackbuilds|SlackBuilds]] in the next section. | Read how to use [[slackbuilds|SlackBuilds]] in the next section. | ||
| - | [[{arrown.png|border:0;background:none;width:0;display:inline-block;float:right;}slackbuilds|]][[{arrowp.png|border:0;background:none;width:0;float:right;}linuxaudio|]] | + | <WRAP centeralign> |
| + | <wrap fa>[[linuxaudio|R]]</wrap> <wrap fa>[[start|S]]</wrap> <wrap fa>[[slackbuilds|Q]]</wrap> | ||
| + | </WRAP> | ||