[pkg-go] gbp: how to import upstream tarball without tag?

[Dmitry Smirnov]

On Wednesday 02 September 2015 12:52:56 Martín Ferrari wrote:
> There is a very well documented and tidy process for doing all this,
> although it is probably way too complicated for most people. Still, it
> is a good read to have an idea of how to do things:
> http://blog.mycre.ws/articles/git-packaging-workflow-for-py-lmdb/

Thank you for detailed replay and for all your hints. Indeed I find it too 
complicated. :( I merely cloned one of our packages' repository and managed 
to produce a release tarball from HEAD of upstream repository by using "dh-
make-golang" which is a bit awkward yet a lot simpler than to configure git 
remote and fetch history of all upstream changes since beginning of time 
merely to generate tarball for "gbp import-orig"...


> Another read: DEP-14, which documents some best-practices for debian/git
> packaging: http://dep.debian.net/deps/dep14/

IMHO this is too GBP-oriented approach. My favourite layout of debian package 
repositories is documented here:

    https://pkg-kde.alioth.debian.org/gitguidelines.html

Unfortunately it does not answer the question how to easily produce orig.tar 
from tagless GitHub repositories...

-- 
Regards,
 Dmitry Smirnov.

---

Good luck happens when preparedness meets opportunity.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20150902/49319ef5/attachment.sig>