Hello, On Mon, Aug 15, 2016 at 09:24:01PM +0500, Andrey Rahmatullin wrote: > > Do you have a example or a wiki in mind ? > Um. git archive <commit ID> | xz > foo.tar.xz, I guess. One thing I've done is added a tag corresponding to upstream part of the version in my Debian changelog entry. Then gbp can generate the tarball for me. For example, support I'm packaging 0~git.abc123d. This version number might be used because I'm basing my packaging on upstream git commit whose hash is uniquely identified by the string 'abc123d'. I would add a tag '0_abc123d' (since gbp replaces '~' with '_' in tags due to git restrictions). Then `gbp buildpackage` would generate the tarball as needed. Just calling `git archive` yourself is fine. The only advantage of the method I just described is that it's easier to remember/document for future releases -- create the tag, and let gbp do the rest. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature