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.
Slackbuilds does not have updated version of qbittorent,libtorrent-rasterbar and xca. All the build scripts are for older versions. src2pkg does not convert any of the packages. So how can I update them, when I run them manually, I get errors and when I run src2pkg same thing happens.
You can manually change the SlackBuilds to work with the newer versions. Sometimes all you need to do is pass a new VERSION variable, but sometimes newer versions require additional dependencies and/or configure options. As for SBo, it is up to the maintainers to put out updated versions. I know I am not constantly checking the SlackBuilds I maintain to see if there's new versions, so I wouldn't mind if someone were to email me to let me know there's a newer version. So, the maintainer is listed on the SBo page and in the .info file, so it might be a good idea to let them know there's an updated version. It could also be possible that the maintainer is aware of the update and hasn't had time to work on it, chose to keep it at a specific version for a specific reason (dependency for another program or issues with building).
Best thing to do is contact the maintainer and see what they say. As to src2pkg, I haven't used that in years, so without an actual error message, I can't venture a guess on what's going wrong.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.