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.
Hello! I want to know what we like to see in Slackware tree.
As for me, i want to see proxy server (maybe squid), jabber server (maybe openfire), and more another...
Click here to see the post LQ members have rated as the most helpful post in this thread.
Hello! I want to know what we like to see in Slackware tree.
As for me, i want to see proxy server (maybe squid), jabber server (maybe openfire), and more another...
I'm satisfied with Slackware as it comes. If something is needed then I just get what is needed at Slackbuilds.
PV & Team do have to cut things off somewhere. That's why we have Slackbuilds to provide additional packages that are built by Slackware users for the Slackware community.
Last edited by onebuck; 06-07-2011 at 08:15 AM.
Reason: database error correct format & spelling
PV & Team do have to cut things off somewhere. That's why we have Slackbuilds to provide additional packages that are built by Slackware users for the Slackware community.
Yeah, but in Slackware tree many other servers, but there is no proxy and jabber for example, but there are yet two or more DHCP server...
I agree onebuck. Slackware ships with an excellent complement of programs. If I need additional applications I will peruse the above-mentioned links.
Also, rworkman provides excellent Slackware packages. Robby is one of our Slackware developers; his packages are also completely trustworthy.
I consider the two most important ones, a seperate xulrunner (maybe along with nss and nspr) instead of using seamonkey and libreoffice. Texlive would be nice too.
But the chances of seeing the later two any time soon are pretty slim, since their sources are huge.
The fakeroot program allows you to build packages without root privileges. If you make a mistake in writing a build script, you don't accidentally modify system files.
The fakeroot program allows you to build packages without root privileges. If you make a mistake in writing a build script, you don't accidentally modify system files.
If you just build a package no system files will be touched. If you are modifying a build script then do so from a copy of the original. If you are satisfied with the build then doing the installpkg will modify.
If you make a mistake in writing a build script, you don't accidentally modify system files.
This reminded me an incident I had a few years ago, when I was working on some SlackBuild and accidentally left one variable undefined. The problem was the line below, something like rm -rf $FOO. Ended up losing almost all of my system partition, luckily my personal files were left intact.
That's why it's crucial to test those things in some sort of isolated environment. And have backups.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Programs, what you like to see in Slackware tree
