SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
It is unlikely that you, as an unknown newbie to the forum here, who has not yet produced anything and for unspecified reasons is apparently unwilling to work with SlackBuilds.org (a perfectly good, well-managed, and already existing project) will be gaining my trust any time soon. Whether you gain anyone else's remains to be seen.
Well, I will be not doing that to get reputation, I'm just motivated to do it if I get help. And since a while I started going deeper on this topic about building packages, then I compared other repos with ours and we don't have that much packages, as I said before I was not trying to put Slackbuild down nor get hypy, and I could also work with Slackbuild, but first I will try to express my ideas here and if someone got interested i could show even better. My point of view was simple:
If we are a big community when not the biggest after Debian/Ubuntu, why do we have a low number of packages a not so much people interested in doing it? Linuxpackages.net was a pretty good package source time ago, now is dead, in combination with Slackbuild it was enough. Why not try to put more packages online? and you could tell me what is so important for you in the scripts and I follow that as strict as possible, even if I wouldn't release it in a project, at least it will be a great help, to know what really matters.
Since majority of slackware users are english speaker, and the default language of slackware is english (Last time I installed slackware, you can't put the installer in French or in Italian), I think it would be more representative of slackware if the only decent binary package repository would be in english.
I should try to contact slacky admins to propose help for an english translation of their web site, if they are intereseted.
Like I said before, it isn't more acceptable to pass the website to a translator. It is a work-around, but not a definitive solution in my opinion.
In addition to SlackBuilds.org and slacky.eu communities, there are also these (977) packages in the SalixOS repos, which typically work without issue on vanilla Slackware. There are several people on this forum that use binary packages from the SalixOS repositories with regular Slackware (myself included). They also provide build scripts if you want them (albeit primarily in SLKBUILD format).
I see little reason to create yet another repository, rather than working with SBo, Slacky or SalixOS, all of whom accept external contributors (I myself have made minor contributions to both SBo and SalixOS in the past, neither of which required unreasonable amounts of effort). In the case of SalixOS they also provide a binary repository with several mirrors and they are relatively flexible in that they will allow to submit packages in SlackBuild format if you don't want to use their own slkbuild utility.
Last edited by ruario; 03-23-2013 at 03:20 PM.
Reason: Added current package count
Don't know if anybody has already suggested this - but I'll add my vote for PostgreSQL. Great database system and much "free'er" than others ;-). I'm perfectly happy with the SBo build - but if it could be included by default it would be great. It would also save me from having to recompile PHP for it :-)
I'll also vote for Exim (or at least Postfix, if that's your thing). I don't want to ruffle anybody's feathers - but as a sysadmin who got into Linux only in the last decade or so - I just couldn't muster enough masochism to learn Sendmail. Then again - there might be other reasons for having Sendmail around - such as legacy setups - so I'll just quietly go back to my corner :-)
I'll also add a vote for including ntfs-3g in the install disc. It is amazing how many times I've used the Slack install disc as a quick rescue disc - and the lack of ntfs-3g / ntfs-rw capabilities is the main stumbling block I hit - having to switch instead to the install disc of that popular distro whose name starts with "U" - but I won't say which.
Then again - the Slack install disc is not really meant to be a rescue disc I guess - so I'll accept it if I'm told that's not really an appropriate request for the install disc.