Originally Posted by Spinlock
sbopkg only works with SlackBuilds.org scripts, not the main Slackware build scripts.
I hear this a lot but the whole truth is that sbopkg works with SBo-compatible hierarchies and scripts (which may be what is meant but a new user probably wouldn't understand it that way). For instance, you can have a local repo of non-SBo buildscripts. (I have fvwm 2.5.x (since it's not suitable for SBo because fvwm 2.4.x is an official Slackware package) and so on.)
<digression>Also, while there's no sense in trying to use sbopkg to rebuild Slackware (there's no sense in rebuilding Slackware at all - it's not a linear process and you'd be missing Slack's mojo anyway), you can get as far as dumping Slackware's source directory into local (or linking it to local) and ending up with a pile of some of the packages. At least 'sbopkg -V local -e continue -b ed -b time' build those two packages and deposited them in /tmp/SBo.
Slackware builds don't have info files and, unless they were originally SBo scripts, Slackware scripts don't have the OUTPUT variable (which sbopkg currently relies on in a critical spot) and some apps (like bsd-games) don't respect much of anything you tell them and so on. So there are errors with all packages and serious ones with some of them and, as I say, no point in it even if it would work. So I'm not suggesting doing this.
I'm just saying that sbopkg is intended to build personal/compatible stuff and, with a little bull-headedness, can be made to do things it isn't even intended to do. It's even possible to edit the SlackBuild to produce customized output
Just file this digression under the 'stupid' part of the principle that 'UNIX was not designed to stop its users from doing stupid things, as that would also stop them from doing clever things.'</digression>