Slackware tools do not provide dependency resolution for packages
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.
Awesome! And what hitest just said is correct. Since 13.37 I've been using Slackware as my main Linux install. I have deviated a couple times, but keep coming back to Slackware. It works, it's fun, and the guys here are great.
With slackpkg and sbopkg I can install/update pretty much everything I need. If I can't find a software on slackbuilds.org I use src2pkg or rpm2tgz to create my packages and it works fine. One thing I really dislike on debian and all "apt" distros is that it seems that apt is always trying to destroy your system.
Congratulations! Once you Slack, you never go back. Welcome to our forum!
Not all of us "stay" with Slackware, but we use Slackware for other purposes like those of us who use LFS. If it wasn't for Slackware, I'd have never gotten into LFS. I would probably consider myself a Slackware Allumni User. To me LFS is, in my opinion, the next and possibly final step after Slackware, but I have to say, Slackware taught me EVERYTHING I'd need to know. No other distribution offered that.
If I ever ran into Patrick, I'd probably buy him a beer, shake his hand, and say "Thank you".
If you keep logs of what you install and add to the system, updating LFS is about as easy as updating Slackware... Just a little more involved as you'll have to update dependencies and packages in sequences and build packages.
Otherwise easy or hard is what you make of it. Just like Slackware, but if you have enough experience with Slackware knowing what all to do should be second nature.
Sometimes I think about building a simple desktop system, I only need a few things like: i3, firefox, a file manager, a media player and a torrent client. I am happy with slack but I think LFS/BLFS might be fun.
When you go to slackbuilds.org and find what you like it will just about always tell you the dependencies needed just install them first. There are several different places to find pre built packages ready to install if you wish. Aliens and ponce is just 2 of those.