On May 29 2019, Sam Hartman <hartm...@debian.org> wrote:
> I'm certainly going to look at dck-buildpackage now, because what he
> describes is a workflow I'd like to be using within Debian.
>
> For some projects I want to ignore orig tarballs as much as I can. I'm
> happy with native packages, or 3.0 quilt with single-debian-patch.
> I don't want merge artifacts from Debian packaging on my branches.
> I'm happy to need to give the system an upstream tag.
> I'm happy for a dsc to fall out the bottom, and so long as it
> corresponds to my git tree I don't care how that happens.
> I have a slight preference for 3.0 format over 1.0 format packages. 3.0
> makes it possible to deal with binaries, better compression and a couple
> of things like that. The quilt bits are (in this workflow) an annoyance
> to be conquered, not a value.
>
> The thing his approach really seems to have going for it is that he
> gives up on the debian history fast forwarding and instead rebases a lot
> for a cleaner history.
> If we could figure out a way to collaborate on something like that well,
> it might be a very interesting tool to have.
This sounds similar to the (now unmaintained) git-dpm to me.
Best,
-Nikolaus
--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
