Git packaging for orig.tar.gz style packages

[Kumar Appaiah]

Dear vcs-pkg,

I have been pestering Martin to add documentation on how to adapt his
Git packaging methods for the "subdued" Debian maintainers who really
don't fetch upstream code from the upstream development repos and use
the .orig.tar.gz approach. During my search, I came across Martin's
earlier post on this topic:

http://lists.madduck.net/pipermail/vcs-pkg/2007-June/000001.html

While it looks fine, I feel uncomfortable about this line, when he
imports a new upstream release:

 # new upstream incorporating feature branch
 $ tar xfz ../gruezi_2.2.orig.tar.gz
 $ mv gruezi-2.2/* . && rmdir gruezi-2.2

The mv gruezi-2.2/* && rmdir is not nice, IMHO. Won't that be
incorrect if upstream removes some files from their original tree?
This doesn't ensure that we remove it from our directory, does it?

Of course, further inspection of the .diff.gz's diffstat might reveal
this fact, and we can correct it. But isn't this still a trifle
inelegant?

Of course, we could add a check by comparing the list of tarball files
against what we have now, but I wanted to know if someone has a better
idea.

Thanks!

Kumar
-- 
Kumar Appaiah,
458, Jamuna Hostel,
Indian Institute of Technology Madras,
Chennai - 600 036
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/attachments/20071013/027dfd15/attachment.pgp