Raphael Hertzog writes ("Re: Bug#722546: dgit should not pass -i\.git -I.git to
dpkg-source"):
> So maybe you believe that my git tree is not suitable for use with dgit
Precisely.
> > The principle behind dgit is that you don't have to worry about any of
> > this. The git tree provided and used by dgit is exactly correct.
>
> While this might be ok if you start with "dgit clone", many existing
> packages do already have a git repository. And when you "dgit pull"
> in such a repository, your git tree will be "tainted" by whatever
> the maintainer might have done to it.
DDTT.
> The nice thing about dgit is that it offers a gateway between git and
> direct work in a source package, but if that gateway adds arbitrary
> restrictions, then it becomes less useful.
These "restrictions" are IMO essential.
> > I think the current behaviour serves those users well. Your implied
> > proposed change would serve those users less well.
>
> How so?
Someone doing an NMU should be able to use exactly the existing
source-package-based workflow, except with the assistance of git. In
your proposal an NMUer needs to know what strange things the git tree
might contain.
Ian.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
