[SOLVED] Keeping updated the packages installed via sbopkg. A couple of questions.
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.
Keeping updated the packages installed via sbopkg. A couple of questions.
Hi slackers....
I am really enjoying recently slackware. Using slackpkg and sbopkg it is so easy to keep slackware running current. Sometimes I feel like a master of Linux, which is absolutely no true.
Apart of some objectives I have regarding slackware's philosophy, I have this question please. I have about 8 packages installed via sbopkg. my question.
1)Is there a way to keep these packages updated via a program? (If not I guess I am obliged to check manually for each of them.)
2) Also, sometimes when we build a package via sbopkg it is necessary to build other packages. Is there an option to install via sbopkg and the package and its dependencies required through just one command?
1) Updating to the latest and greatest isn't necessarily the right way to do it. Unix people (and especially slackers) tend to be conservative and there's no promise that the latest version of a product is the best (remember Windows ME, Windows Vista ?). We tend to stick to a version until there's a good reason upgrade. And that's the point - when you really do have a good reason to upgrade, then you'll know about it.
2) Look the the queue files (http://gitorious.org/sbopkg-slackwar...ball/sbo-13.37). Unpack these in a directory and tell Sbopkg where they are. Then, when you build, look for the matching queue file and load that - it will have the dependencies. If you have been diligent and stuck to slackbuilds.org, your previously built packages will be shown and you won't need to rebuild them again (unless you add more features).
Thank you guys. slackpkg -c was the info I needed.
Regarding the package building together with its dependencies, if I understood correctly there is no similar command such as sbopkg -option (build all required)? I should continue adding manually all its dependencies to queue right?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.