On Wed, Dec 02, 2015 at 02:41:20PM +0000, Ghislain Vaillant wrote: > You can have a look at the ArrayFire package that I personally maintain, > which also relies on submodules.
Thanks a lot for the prompt answer and for the hints, Ghis, as well as for the pointer to the ArrayFire package: it's been very helpful and informative! Unfortunately, I still have some follow-up questions after spending some time testing and reviewing the documentation for gbp and related tools. > - Use the upstream git repository and gbp with the --git-submodules option > (which is the solution I use with ArrayFire). I have been trying to follow this route, aiming to have a minimal working example of a repository that produces a package with the submodules fetched: $ git clone --no-checkout -o upstream https://github.com/jamesturk/jellyfish.git $ cd jellfish $ git checkout -b upstream/v0.5.1 0.5.1 $ git checkout -b debian/sid 0.5.1 $ mkdir debian; vim debian/... (debian/gbp.conf includes submodules = True on buildpackage section) $ git add debian; git commit -a At this point, my struggle is how to have a proper pristine branch - is there a way to use "pristine-tar commit" with the upstream .orig.tar.gz file, that fetches the submodules when building the package? The closest I get is: $ git-buildpackage --git-no-pristine-tar --git-submodules --git-upstream-branch=upstream/v0.5.1 But I'm not sure if this kind of defeats the purpose, as the generated .orig.tar.gz differs from the upsteam one by including the submodules contents. Could you please let me know if there is a better, more solid approach? Best regards, and thanks again! -- Diego M. Rodriguez 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232
signature.asc
Description: Digital signature
