On 13 October 2014 00:19, Barry Warsaw <ba...@debian.org> wrote: > Maybe not mutually exclusive, but what's the point? I certainly would not > base the Debian packaging on anything but the upstream tarball, and most git > workflows provide those as an unpacked upstream source branch. Does upstream > vcs add value?
I would expect it to make merging / rebasing Debian patches on top of a new upstream version easier, since you have the granular history of changes to the source tree, not one massive single commit which may not be accurate (eg. renames of change files may not be detected etc.). On the flip side, if there are few or no patches to the upstream source, then it probably doesn't matter much at all. > In any case, if upstream vcs is included in the team git repo, then I think > it's incumbent on maintainers of those packages to document that in > README.source (both how it's done and *why*) and to ensure that notifications > of upstream commits are suppressed to team mailing list and IRC. I do think the benefits of team maintenance are diminshed quite a lot when packages need to have such specialized instructions, so aiming for a standardized workflow / configuration (*whatever* that might be!) is valuable. -- mithrandi, i Ainil en-Balandor, a faer Ambar -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/camckhmtkd09xajtrnxtcxj6qdbpfmaqxjwoqdbycx1twdhb...@mail.gmail.com
