Re: Status of dgit (good for NMUs and fast-forwarding Debian branches)
Ian Jackson <firstname.lastname@example.org> writes:
> I should also mention a non-goal:
> * I have no plans to support a workflow where dgit's git tree
> contains different contents to the source packages.
> My view is that the source code is the source code. If something
> is not needed for [d]git users then it is not needed in the Debian
> soure package either; conversely if you need to put something in
> the Debian source package then by definition it is source code and
> should be in your vcs too.
> Furthermore, because dgit's need to bidirectionally gateway between
> git and the archive, it is difficult for dgit to do this properly.
> For example, if there are files in the source package that weren't
> in the last git commit pushed with dgit, then the git trees
> synthesised by dgit from source package (which dgit fetch/clone
> makes when the last upload was not done with dgit) would contain
> those files. So the files would seem to have been created by the
> non-dgit-using upload.
I believe, if I understand this correctly, this will cause problems for
the use of local-options and local-patch-header to set single-debian-patch
for maintainer uploads.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>