![]() ![]() There is also a mailing list and an irc channel available if you have info file that tell you the version, sourceĭownload location, md5sum, supported architectures and the author of the In the slackbuild archive are the build script, license information. The script repository houses user submitted scripts forīuilding stable applications for Slackware that have been tested on variousĪrchitectures by knowledgeable members of the Slackware community. ![]() Run and the package has been built you then have a redistributable packageįor the specified application that fits your specific needs. Modify the script and arguments to fit your needs. Options/modifications that were done to a package and if you need you can This availability in the source directory, allows you to view all Has a slackbuild file, in the source directory on the Slackware disk you willįind the slackbuild files and source code for every officially supported This is the true magic in Slackware, every official package that you receive Listed below are the Unofficial tools and a brief explanation of their The best comparison for package building tools is toĬompare them to the portage system that is used in Gentoo Linux. Instructions to utilize the resulting binaries and build a Slackwareįormatted package that properly interacts with the Slackware package Once the application has been compiled, the scripts pass the proper Retrieval tools but rather than downloading a pre-build package they retrieveĪ build script (which can be customized) and the subsequent source codeĪllowing the user to custom compile an application for their system and their In contrast the package building tools are somewhat similar to the package Have been set by the user and allow the user to search the repositories toĭownload and install pre-configured packages. These package retrieval tools call to specific online package repositories which Yum, apt-get, urpmi and various tools which are used in other distributions. The package retrieval tools have a functionality which is similar to YAST, These tools can be broken into two groups The unofficial tools are tools that were made by third parties which are not Slackware packages can be found with any of the following extensions: Has been developed by those who know the functionality of the applications Uptime, with Slackware these issues cannot happen as all code that is used Head when running a production system which requires heightened security and Liability is something that an administrator does not want hanging over their Were not responsible for the changes or aware of the changes. Result in exploits that only effect the specific distribution which canįor some time because the original authors (those who know the applications best) Source code with their own revisions prior to distribution, this can addĪdditional functionality but in some cases such as the Other distributions such as debian and redhat choose to modify the original To update databases, font or icon caches to include the newly installed (executables for windows managers) and running installed applications/scripts Modifications that are made for the packages are adding. Original source code in which only official patches are applied, the only Remove functions from software beyond the author's design, unless a small Means is that the Slackware community does not modify the source or add and ![]() In terms of security and accountability Slackware is excellent because itīrings you software in the condition that the authors intended. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |