sbopkg missing 'feature'
by bifferos from LinuxQuestions.org on (#4ZMC3)
I'm using sbopkg to compile packages. I've followed the instructions to make it use the Ponce repo, and it's working great.
There are a few issues I've encountered:
first, sqg -p <package> doesn't seem to work (no packages are found). Clearly other people have made it work since I've seen lots of examples of this both on forums and in the documentation. I'm wondering if the latest version is broken?
Secondly, there seems to be some bits missing from the system as a whole when compiling lots of packages. Usually when I find something missing from the Slackware ecosystem there's a bunch of people who've implemented it in their own ways, so I'm curious to know how people are solving this.
As an example google-go-lang shares a binary name with the gccgo compiler. This means some action is required, not before building, but before using the package as a dependency to ensure this is first in the path, or there will be issues if the dependent package requires google-go specific functionality.
So the first issue is solved by a script that gets run after build, but only where a dependent is going to be built. It's not strictly an 'after' script.
The next issue is exemplified by mongodb. A user and a group *must* be created before the build script runs. In this case this is a simple 'before' script, it needs to be run before the build, if the user/group hasn't been created.
I honestly have no idea how many other packages have these kinds of quirks, and maybe it's uncommon, but I can think of a few solutions.
The quick solution (for me) is to maintain a parallel directory structure to the slackbuilds repo in my own repo, with scripts to do the right thing before and after the builds. I wonder if anyone else has concocted something similar before I reinvent the wheel?
There are a few issues I've encountered:
first, sqg -p <package> doesn't seem to work (no packages are found). Clearly other people have made it work since I've seen lots of examples of this both on forums and in the documentation. I'm wondering if the latest version is broken?
Secondly, there seems to be some bits missing from the system as a whole when compiling lots of packages. Usually when I find something missing from the Slackware ecosystem there's a bunch of people who've implemented it in their own ways, so I'm curious to know how people are solving this.
As an example google-go-lang shares a binary name with the gccgo compiler. This means some action is required, not before building, but before using the package as a dependency to ensure this is first in the path, or there will be issues if the dependent package requires google-go specific functionality.
So the first issue is solved by a script that gets run after build, but only where a dependent is going to be built. It's not strictly an 'after' script.
The next issue is exemplified by mongodb. A user and a group *must* be created before the build script runs. In this case this is a simple 'before' script, it needs to be run before the build, if the user/group hasn't been created.
I honestly have no idea how many other packages have these kinds of quirks, and maybe it's uncommon, but I can think of a few solutions.
The quick solution (for me) is to maintain a parallel directory structure to the slackbuilds repo in my own repo, with scripts to do the right thing before and after the builds. I wonder if anyone else has concocted something similar before I reinvent the wheel?