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, unfortunately, have the SBo extension for packages that aren't in the slackbuilds repository.
Me too (they are slackbuilds that have not yet been submitted) and, unfortunately, I sent some corrupt data (two packages with wrong tag) when trying to remove them. Sorry bosth!
First, I am using exclusively Slackware from 1995 until today and more.
I am using frequently slackbuild for the add-on packages.
I cannot tell you exactly how, but I have many of SBo packages.
On my 64bits computer, around 8. On others, depending the
job done by those computer, some or many of them.
The scripts are very handy, I dont have much time doing such packages.
With slackbuild, I just let the script doing his job. It's very easy.
And don't forget to mention, it work!!!
Slackware is a great distrib. Slackbuild, the best add-on that we
can put into it.
Me too (they are slackbuilds that have not yet been submitted) and, unfortunately, I sent some corrupt data (two packages with wrong tag) when trying to remove them. Sorry bosth!
Corrupt submissions are usually detected and removed during processing.
I have several packages tagged with SBo, but in reality I need some time to check dependencies and to do 'secretary' job before submittion and approval
only 125 machines using Slackbuilds? it is hardly true. I believe the number must be 100 times more at least. Most people do not respond to this survey.
By the way, just look the site report for Slackbuild:
@Ramurd - on traditional Unix boxes (eg Solaris, AT&T SVR4, etc) /tmp does not survive a reboot. Thus after a clean boot, /tmp is empty. I've always wondered why Linux has never done this. Easy to remedy of course - merely add a few lines of 'rm /tmp/*' and
'rm /tmp/.*' to one of the early startup scripts.
I know both of those; and in fact I do clean up /tmp on a regular basis, just not automatically. Fact remains that I dislike the fact that SBo builds in /tmp; I prefer my own setup: $(cwd)/src, $(cwd)/pkg, $(cwd)/tgt (the latter only for those cases where it is not allowed to build in the source directory); in $(cwd) I have the source-tarball, slackbuild script, slac-desc and whatever else is needed to create the package. The slackbuild-script I have a template for as well, that uses functions, rather than a long sequence of commands. Which allows me to do partial (re)builds and makes it easier to reuse pre-defined code. Works like a charm for me ;-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.