Name Last modified Size Description
Parent Directory 05-May-2009 21:31 -
IMPORTANT 09-Sep-2004 22:48 1k
WHATS-WHAT 12-Dec-2004 23:13 2k
filesize 27-Oct-2003 16:33 1k
generic.builder/ 09-Sep-2004 21:23 - build directory
slack.10.0.builder/ 12-Dec-2004 22:58 - build directory
slack.8.1.builder/ 09-Sep-2004 21:29 - build directory
slack.9.0.builder/ 09-Sep-2004 21:29 - build directory
slack.9.1.builder/ 09-Sep-2004 21:29 - build directory
slackintosh.builder/ 09-Sep-2004 21:30 - build directory
* NOTE: DUE TO LOW BANDWIDTH MOST SOURCE CODE TARBALLS ARE EMPTY AND DISPLAYED FOR INFORMATION ONLY.
YOU WILL NEED TO OBTAIN THE REAL TARBALLS YOURSELF BY (FOR EXAMPLE) SEARCHING
FRESHMEAT.NET
ABOUT SLACKBUILD CENTRAL
Many people like rolling their own packages. But most don't have the time or inclination to work
out the optimal configure and build options for each package.
Using other people's SlackBuild scripts is the obvious solution, yet sites
such as
LinuxMafia.org
(now
LinuxPackages.net)
tend NOT to include SlackBuild scripts in source directories (if there's
a source directory at all). In fact, these sites often use non-standard
building formats such as
checkinstall,
protopkg
and
customised SlackBuild spin-offs.
While these do have a certain appeal, non-standard package-building formats
need to be configured and built themselves. And even then they sometimes simply
"won't work" with certain types of tarballs.
Not so with SlackBuild scripts. Because each script is written to
suit each individual package, it's guaranteed to work with any "compileable" source.
Above all, SlackBuild scripts are THE standard Slackware package-building
method. Patrick Volkerding himself created and continues to use SlackBuild scripts
in his latest
Slackware
distributions. And if it's good enough for Pat...!