[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Git packaging workflow discussion on planet.d.o

On 04/04/2013 16:00, Andreas Tille wrote:

as a non-regular planet reader I'd like to move the discussion here.  I
have read the following blog entries

  [1] http://joeyh.name/blog/entry/upstream_git_repositories/
  [2] http://www.eyrie.org/~eagle/journal/2013-04/001.html
  [3] http://thomas.goirand.fr/blog/?p=94

I personally would like to follow Russ[2] most closely because I
consider tarballs definitely as relevant for reasons that are somehow
not mentioned in the blog entries:

   1. Not all Git repositories enable proper watch files (I know
      GitHub does but there are others out there that don't)
   2. Uscan does not support extraction from VCS repositories
      (even if this is a shame and should be fixed fow Wheezy+1
      either in uscan or a to be developed tool say vcsscan)
   3. It is hard to get a MD5sum identical upstream tarball if you
      do not use pristine-tar and MD5sum identical tarballs are
      quite an important thing for teams or sponsor/sponsees

Yesterday, however, I just had the case of a project with no tarballs (as the library I wanted to package is part of a larger project, it's not released independently). I stumbled (too long) on having a good workflow for this (I ended up tagging myself the upstream tree).

Jean-Christophe Dubacq

Reply to: