Originally Posted by kingbeowulf
Also, many of the added dependencies in AlienBOB's scripts are too invasive or not compatible with mainline Slackware-stable. Hence, he "builds in" some of them, and some others are just for convenience (e.g. script grabs and compiles everything automatically in the right sequence). SBo just includes those dependencies that don't interfere with Slackware-stable.
I don't know where you are getting that idea from.
All my packages (compiled using the SlackBuild scripts I also provide) in my repository at http://connie.slackware.com/~alien/slackbuilds/
are 100% compatible with Slackware. I provide packages for multiple stable versions and do not build them for slackware-current generally. The packages in this repository are add-ons to Slackware, i.e. the packages do not conflict or replace anything in Slackware (with some exceptions like MPlayer for which I also wrote the official Slackware script).
I have other repositories, like "ktown" at http://alien.slackbook.org/ktown/
where I provide more up to date versions of KDE than you can find in Slackware. The ktown repository will
replace a lot of official Slackware packages... naturally.
There is also my multilib repository at http://connie.slackware.com/~alien/multilib/
where I provide replacements for Slackware's own gcc and glibc and provide add-on packages which make it possible to run and compile 32-bit software on 64-bit Slackware.
Those are three separate repositories, with three different goals.
I always provide SlackBuild scripts, patches and sources so that you can try and build the packages yourselves, but the main purpose is to provide packages
. The http://slackbuilds.org/
site has a goal which is opposite of this: that site provides only the SlackBuild scripts and expects you to build the packages (and with the use of sbpokg
and its queue file system, that is not complicated to do).
I will not submit my SlackBuild scripts at http://slackbuilds.org/
because as others stated already, my scripts are coneptually different, and do things we do not want from a script at SlackBuilds.org (like downloading missing source tarballs automatically, or building static packages which use a lot of different sources - like VLC). I am an admin at http://slackbuilds.org/
but I keep these businesses strictly separated.