On Mon, Oct 28, 2019 at 01:14:39PM +0100, Andreas Ronnquist wrote:
> Hi
>
> I am packaging a game (opensurge), which has a repository on github.
> My problem is that it is dependent on another package (surgescript, a
> scripting language for it), which also has it's own tarball and
> repository on github.
>
> Surgescript is distributed as a library (statically built).
>
> Do you think it's reasonable to repackage this into one tarball, and
> use that as upstream, statically linking the surgescript library?
>
> To me this looks like the best idea, but I am very much open for
> suggestions.
>
> Also, git-buildpackage isn't equipped for dual orig tarball yet, right?
You could use components: keep the opensurge source in its own tarball,
opensurge_X.Y.Z.orig.tar.xz, and put the surgescript source into its
own tarball, opensurge-X.Y.Z.orig-surgescript.tar.xz; this will make
dpkg-source (and everything that uses dpkg-source) extract the
surgescript tarball into a surgescript/ directory of the extracted
opensurge source. FTR, gbp-import-orig supports this if you pass one or
more --component options specifying the additional tarballs.
This is the way I would do it - no need to modify the original tarball,
no need to modify the additional tarball, just maybe make some small
changes to the build process because things are in a slightly different
directory tree structure.
G'luck,
Peter
--
Peter Pentchev roam@{ringlet.net,debian.org,FreeBSD.org} pp@storpool.com
PGP key: http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
Attachment:
signature.asc
Description: PGP signature