Re: Preferred git branch structure when upstream moves from tarballs to git
On Thu, 2019-05-02 at 13:45 +0100, Ian Jackson wrote:
> Ansgar Burchardt writes ("Re: Preferred git branch structure when
> upstream moves from tarballs to git"):
> > On Tue, 2019-04-30 at 16:00 -0700, Sean Whitton wrote:
> > > As a package maintainer, if you don't keep the whole source package in
> > > git, you're giving up on a lot of the power of git.
> >
> > I think keeping entry barriers low is more important than being able to
> > use all the power of Git. That's sadly one of the main problems with
> > Dgit: it raises entry barriers by making packaging more complicated.
>
> A source-only upload with dgit is fewer commands, and more reliable,
> than doing so with sbuild/dput.
Complexity is not the number of commands to use.
Having to know about branches, merging, dealing with multiple remotes,
... *is* an entry barrier compared to not having to know about it. Now
you have to teach people that before you even get to how to write a
build recipe.
(Also for source-only uploads you don't need sbuild at all.)
> Doing an NMU campaign with dgit is massively easier than doing so with
> .dsc-based tools.
Why should that be "massively easier" with dgit? Without dgit you get
source, change the source package, build the source package, upload the
modified source package. No matter what workflow/VCS/* the maintainer
uses.
Ansgar
Reply to: