[Slackbuilds-users] Deal with source that requires submodules
B. Watson
urchlay at slackware.uk
Fri Jul 29 04:42:09 UTC 2022
On Fri, 29 Jul 2022, Christoph Willing wrote:
> Although there's an easy solution in this particular case, I would be
> interested in hearing of a more general solution for cases where there
> is no such additional tarball available.
>
> I maintain another SlackBuild which has exactly the same problem. My
> solution so far has been to locally checkout the commit which
> corresponds to the (incomplete) release tarball. Then I pull in the
> required submodules and generate a new (complete) tarball which I host
> at slackbuildsdirectlinks, from where can be used as a single download
> for the SlackBuild.
>
> While that's a workable solution, I would definitely be interested in
> alternatives.
That's what I do, too: generate and host a tarball. Generally there's
a git2tarxz.sh script in the directory with the SlackBuild (in SBo
git, so it won't get lost).
More information about the SlackBuilds-users
mailing list