On Wed, Apr 17, 2013 at 3:27 AM, Hans-Christoph Steiner <h...@at.or.at> wrote: > On 04/06/2013 03:32 AM, Reinhard Tartler wrote: >> Hi, >> >> Recently, Russ' blog post was echoed on http://planet.debian.org: >> >> http://www.eyrie.org/~eagle/journal/2013-04/001.html >> >> In that post, he describes how to combine both the "import tarball" >> and the "have upstream history" available in the upstream packaging >> branch. AFAIUI, the heavy work is implemented in git-buildpackage's >> --upstream-vcs-tag <tag> option. >> >> While that option is news to me, I wonder if maybe anyone else already >> experiments with this? Does the team feel that making it mandatory for >> our package would be beneficial and appropriate? >> > > It sounds very promising, but I think its too soon to mandate it. I think > people should all try it and then report back on experience with it. If no > one hits major hurdles, then mandate it. > > I'm going to try my first package in this style: > http://anonscm.debian.org/gitweb/?p=collab-maint/python-qrcode.git
I've implemented this on rtmpdump: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/rtmpdump.git In order to implement it, I had to use the debian/get-git-source.sh script, which I have simplified a bit on this occasion. After that, this approach basically "just" requires passing the --upstream-vcs to git-import-orig, which I could point to "FETCH_HEAD" (rtmpdump upstream does not seem to believe in neither releases nor tags). Comments welcome. -- regards, Reinhard _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers