SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I like using sbopkg, although I sometimes run the build scripts from Slackbuilds from a command line. I've totally messed up my computer several times, upgrading to -current, and I did it again last night. Instead of repairing the install, I opted to reinstall with a Slackware -current oso from Alien Bob's repository. I have /home on a separate partition, anyway. So gcc is several renditions newer and I'm wondering if running sbopkg that was already compiled and packaged with the older version will play well with the newer compilers and the newer compiled software in Slackware -current.
Distribution: slackware 15.0 64bit, 14.2 64 and 32bit and arm, ubuntu and rasbian
Posts: 495
Rep:
sbopkg is a script. no compiling needed.
You may want to redo packages created using it though, to "benefit" from gcc updates, if that was your question.
sbopkg is a script. no compiling needed.
You may want to redo packages created using it though, to "benefit" from gcc updates, if that was your question.
Yup, that's what I was thinking. I had saved a lot of the packages compiled under the older versions of gcc. So, when I got to looking at recompiling and repackaging some of them with sbopkg, I wondered if it might be better to recompile it as well. Surprisingly, Slackbuilds.org does not have a script for compiling and packaging sbopkg. Is that ironic?
Surprisingly, Slackbuilds.org does not have a script for compiling and packaging sbopkg. Is that ironic?
I think it makes sense. slackbuilds.org is a third party repository of SlackBuild scripts which run fine from command line. Since it's third party, this is the reason why Slackware doesn't recommend it explicitly. Yet it has clean policies, sticks to the KISS principle and is seen as the de facto extension to vanilla Slackware (with the notable exception that is AlienBOB's personal repo). sbopkg is a third party tool for slackbuids.org scripts (but not the only tool), so probably this is the reason why it isn't mentioned on SBo explicitly as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.