[Mergebot-discuss] Consider using dgit instead of gbp

[Sean Whitton]

Hello,

Consider using dgit instead of gbp.  Since dgit is designed to abstract
from packaging repository workflows, you would be able to drop all three
of the things listed under "Assumptions" in your README.

Something like this:

1. existing code to extract patch from the BTS
2. dgit clone package
3. cd package
4. git am < bts.patch or your existing commit code
5. gbp dch
6. dgit sbuild

The user would, after verifying the package, do the following:

1. cd package
2. dgit push

The only problem with this is that your non-dgit packaging repo isn't
updated.  You could do something like `git push --all vcs-git` in that
case and maybe you could provide a helper.  In a lot of cases that would
depend on unreleased dgit functionality to handle patches-unapplied
repositories.

(please keep me in the CC)

-- 
Sean Whitton
-------------- 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/mergebot-discuss/attachments/20160718/6dc252f3/attachment.sig>