Re: Git and tarballs
On Wed, Jul 6, 2011 at 8:38 AM, Wolodja Wentland <email@example.com> wrote:
> Hi all,
> I've recently started to work on some packages and am not sure if I follow
> best practices when packaging software from git repositories with
> My main point of confusion is that I don't really see the need for tarballs
> and what I am doing right now feels a bit clumsy and wrong. As my gut feeling
> is typically a good indicator I feel the need for additional feedback.
> Am I nuts?
> What are your workflows?
> Do you *only* work with tarballs and don't use/track the upstream repositories at all?
> * only use git-import-orig
> * Repository lives only on alioth and all branches track alioth
> If not: How do you work with the *real* upstream branches? How do you generate
I, personally, just use the Debian Github redirector  for my watch
files since my upstreams are good at tagging releases. At that point I
can just use git-import-orig. I don't really need upstream's commit
history in Debian's VCS (since it is available on their own repo), so
this system works for me. Since the debian repositories require an
.orig.tar.gz, my first step of new release workflow is to make sure I
create a proper tarball that is DFSG, and check that into my VCS with
"git-import-orig --pristine-tar". I look at it as the debian git VCS
is to aid in packaging efforts, which revolve around .orig.tar.gz,
.dsc, and .debian.tar.gz - so my workflow is based on creating and
maintaining those files.