[SOLVED] Best practice for running newer version of software than what is available as maintained Slackbuild?
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.
I have been googling queries similar to the topic of this post, but have not had any luck. Maybe my lack of knowledge is missing out on some important keywords.
What would be some suggested good procedure in order to run go-lang 1.5, or if applicable, software in general on Slackware in a situation like this? What steps do I typically need to research in order to accomplish it?
Were it I, I would obtain the sources from a reputable location, preferably the maintainer's website, and compile the software from sources, resolving any dependencies as needed.
Of course you will have to find the sources yourself.
We are at a time where SBo is pretty much frozen pending the release of Slackware 14.2, and this is sort of the holding ground for new SlackBuilds until it is released.
Were it I, I would obtain the sources from a reputable location, preferably the maintainer's website, and compile the software from sources, resolving any dependencies as needed.
Yep. If there is a slackbuild for the package, you can normally get away with modifying that.
If there isn't a slackbuild for the package (In the OP's case, there is one so that won't apply for the OP.), then (IMO) you should try the very excellent tool src2pkg (http://distro.ibiblio.org/amigolinux/download/src2pkg/) to do the build for you.
Thanks for the help! These were all great replies to me - further reading on SlackBuilds that I needed, and a specific solution to the problem in question.
I tried the version from the slackbuilds.org git repo suggested by Skaendo and it worked well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.