git workflows for general Ubuntu development

[Robie Basak]

Hi Sean,

Since our UOS session will start very soon, I'll reply just to the
things that I think I can address immediately for now.

On Tue, Nov 15, 2016 at 10:24:32AM -0700, Sean Whitton wrote:
> The most important part of the tutorial for realising this is putting
> "single-debian-patch" and "auto-commit" in debian/source/options, but I
> would also encourage you to read the section "Sample text for
> README.source".

If this is necessary, then it breaks our use case unless you can also
require all Debian packages to switch to dgit first.

In Debian, a package maintainer can decide to switch VCS system and
write things in README.source to explain how things should be done.

In Ubuntu, switching a package's VCS, debian/source/options, and so
forth would make it increasingly difficult to maintain a delta against
Debian. In general we never add such a (VCS of debian/source/options)
delta. Whatever solution we employ, it must be able to work with
unmodified Debian source packages.

> Like Ian, I beg you to reconsider this in the strongest possible terms!

This will only be possible if dgit actually helps us with our use cases.
If it cannot, then we either need to figure out how to add functionality
to dgit to make this possible, or we cannot use dgit.

I think a path forward might be for our system to be able to take dgit
as input, and also provide dgit as output. But this remains to be seen.

Robie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/attachments/20161115/4bd5397d/attachment-0001.sig>