On 8/25/20 5:41 PM, Sebastiaan Couwenberg wrote: > You're the primary caretaker of the package based on the Uploaders, so > it's up to you. > > The quilt workflow has the benefit that it also works with plain source > packages not managed with git-buildpackage. You should be comfortable > with the quilt workflow in addition to gbp-pg if you need to work on > more packages in the archive like (reverse) dependencies not maintained > within the team. > > The same goes for dch vs gbp-dch, the former works for more use cases > than the latter, hence the preference for plain dch. It also makes it > much easier to choose which changes need to be included in d/changelog > and which ones to have in VCS history only.
Thanks for the input and explanations! In this case I would like to try to go with gbp-pq, because I think the tight connection with the commits and git helps to get it into upstream. Of course, I'm happy to learn and go with pure quilt in other packages - it seems to be very nice handling of patches! Kindness, Felix _______________________________________________ Pkg-grass-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel
