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.
Actually they were built with slackbuild scripts. You can't get the actual files from slackbuild.
So if you want to build your own using slackbuild scripts that's the place to go. SOme people just don't want to or can't build there own, so I offer them here. But they did not come from slackbuild, they say right on their web site that they don't keep pre-built packages there.
From their website::
We do not now nor will we ever provide precompiled packages for any of the applications for which we have SlackBuild scripts.
Yes yes yes. I know that. I've been using Slackbuilds.org for quite a while.
In my experience, building the packages from the scripts provided at the site is a very simple task. If you want to make it even simpler, use the sbopkg utility. Additionally, you did not state how you built the packages (using the SlackBuild scripts from slackbuilds.org) or what might make your packages different or better from what's commonly available (nothing).
So, while you're offer is generous, there does not see to be a lot of value added.
I'm sorry if my response to your first post seemed rude.
I think your offer is a very generous one. However, I only install software on my systems using SBo scripts, Src2pkg, or packages from trusted sources like Robby or Eric. I don't know how you've built your packages. I try to be security-minded when I install software on my Slackware systems.
No offense is intended with this post.
Well, no problem, I just thought I would make the offer. Like I said there are a lot of people, even slack users, that don't like to build from source. No skin off my nose.
Personally, I've been using e17 for years on BW64. Lately, e17 has become much more stable and the developers are making a serious effort to get a stable version of it released in the near future. The road map for e17 is now constantly being whittled down to a stabilized feature set so a release should happen within less than 2 years IMO, maybe within a year ... I'm impressed with the work so much that I haven't looked at alternatives like KDE or GNOME in years... I'm sure your packages will be used and appreciated...