sbomg.lisp (sbo manager)
by slac-in-the-box from LinuxQuestions.org on (#5FZQT)
Howdy Slackware LQ:
I've spent way too much time building slackware packages and way too little time surfing...
There's bound to be other shell scripts shared through the years for managing the building of third party packages from slackbuilds.org -- but, fwiw, for anybody's use or entertainment, here is my work-in-progress:
Code:git clone https://github.com/globaltree/slac-in-the-box.gitInside the slac-in-the-box directory are some readmes and sbomg.lisp (slackbuids.org (sbo) manager). Yes, the script is written in common lisp, and uses steel bank common lisp (sbcl) available from slackbuilds.org.
This is an idealized version that would work in a perfect Slackware ecosystem -- but not every package builds perfectly yet: the culprits are python and jdk.
Since jdk has to have manually-agreed-to license agreement before downloading, sbomg couldn't automate that... so if jdk is dependency to any packages in your list, better manually install jdk before executing sbomg.lisp
and some packages want python linked to python2 and others want it linked to python3, and when its not linked correctly for the build, it fails. Since this is the most common source of failure, I'll eventually get around to an error handler, that will swap the symbolic link for python on failures and then try again; after that, I hope this script will free up some time to chase waves...
Peace,
--Slac-in-the-Box
I've spent way too much time building slackware packages and way too little time surfing...
There's bound to be other shell scripts shared through the years for managing the building of third party packages from slackbuilds.org -- but, fwiw, for anybody's use or entertainment, here is my work-in-progress:
Code:git clone https://github.com/globaltree/slac-in-the-box.gitInside the slac-in-the-box directory are some readmes and sbomg.lisp (slackbuids.org (sbo) manager). Yes, the script is written in common lisp, and uses steel bank common lisp (sbcl) available from slackbuilds.org.
This is an idealized version that would work in a perfect Slackware ecosystem -- but not every package builds perfectly yet: the culprits are python and jdk.
Since jdk has to have manually-agreed-to license agreement before downloading, sbomg couldn't automate that... so if jdk is dependency to any packages in your list, better manually install jdk before executing sbomg.lisp
and some packages want python linked to python2 and others want it linked to python3, and when its not linked correctly for the build, it fails. Since this is the most common source of failure, I'll eventually get around to an error handler, that will swap the symbolic link for python on failures and then try again; after that, I hope this script will free up some time to chase waves...
Peace,
--Slac-in-the-Box