Re: [ANNOUNCE] GIT 0.99.9l aka 1.0rc4

From: Gerrit Pape <pape@smarden.org>
Date: Dec 7, 2005, 16:20 UTC
Message-ID: <20051207162030.18532.qmail@c9a97849515963.315fe32.mid.smarden.org>
In-Reply-To: <7vu0dnb8pm.fsf@assigned-by-dhcp.cox.net>

On Mon, Dec 05, 2005 at 12:16:37PM -0800, Junio C Hamano wrote:

Show 26 quoted lines

> Gerrit Pape <pape@smarden.org> writes:
> > On Sun, Dec 04, 2005 at 01:21:13AM -0800, Junio C Hamano wrote:
> >> *1* It appears Debian finally has an official maintainer, so I
> >
> > Yes, I've taken over maintainership, and introduced the git-core package
> > into Debian/unstable, the git tools previously were included in the
> > cogito package.
> 
> This question is probably relevant only to you and people who
> want to build deb themselves until you package the updated
> upstream, but what is your (and others') preference on debian/
> directory in what _I_ ship?
> 
> I see three possibilities:
> 
>  - Do not care, and keep them as they are as they bitrot.
> 
>  - Remove debian/ from the upstream tree.
> 
>  - You feed patches to me, and I promise you not to touch
>    debian/ area, except adding a new -0 entry at the top of the
>    changelog when bumping the version number up, and perhaps
>    adjusting to the main Makefile changes if the solution is
>    obvious.
> 
> I am neutral between the second and the third.

Normally we suggest upstream to not ship a debian/ directory at all, and I would prefer that. But I can understand that people may got used to it, and prefer to build the packages on their own. So I'm also fine with feeding you with patches, but need to get 0.99.9l into the Debian archive first (already prepared, waiting in a 'new packages' queue), and then adapt the build process to use the debian/ directory in the git tarball, instead of the current tarball-in-tarball approach.

This may take some days, and there are major changes to the debian/ directory as I personally don't use the usual debhelper approach.

Thanks, Gerrit.