Web lists-archives.com

Re: Preferred git branch structure when upstream moves from tarballs to git




Sam Hartman <hartmans@xxxxxxxxxx> writes:
> I'm having a bit of trouble here and am hoping you can help us out.
> Ian asked what git workflow it is that you're talking about where people
> can deal with commit push and pull and don't need to know more.
>
> I didn't see a clear answer to that.
> Which debian packaging workflow do you believe has that property?

There is no need for a vendor branch if only the packaging information
is kept in the repository, i.e. only debian/.  In particular there is no
need for branches or merges for regular updates (i.e. not based on an
older release).

This is also what pretty much every other distribution seems to be
doing, for example Fedora, Gentoo, Ports (BSD), Arch Linux, Void Linux.

It would be easier if there was even more separation between packaging
and upstream source, e.g. base/src (upstream source), base/debian
(packaging information), and possibly other directories below base for
build artifacts (instead of unpredictable locations under base/debian).
Which leads back to the beginning of the subthread[1].

  [1] https://lists.debian.org/debian-devel/2019/04/msg00462.html

Ansgar