Slackware tools do not provide dependency resolution for packages
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.
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.
Don't forget about the new sqg tool from sbopkg 0.37 which can make your life easier dealing dependencies for SBo
you can read how to use it on my SlackBlogs
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
