On Tue, 20 Oct 2015, Brian May wrote: > Barry Warsaw <ba...@debian.org> writes: > > > Now, in practice, it doesn't matter if you ignore git-dpm and just use quilt > > *as long as the final state of the repo is compatible with git-dpm*. > > Meaning, > > in general, you can make whatever local decisions you want as long as they > > don't force other team members to go outside of team recommendations. > > I don't see how you could use quilt and maintain compatability with > git-dpm. git-dpm expects all patches to be in git, and will update > debian/patches automatically from git. quilt writes patches directly in > debian/patches/* and doesn't support git. > > Not something that concerns me personally, quilt was starting to become > very painful for me. I regularly ended up forgetting the "quilt add" > operation before editing files, resulting in invalid patches.
And also for import of upstream tarballs you basically have to use git-dpm as git-dpm keeps state data in debian/.git-dpm whereas git-buildpackage does not have similar state data (except the generic git data like availability of a upstream/<version> tag, and so on). I really regret to not have invested time earlier to try out git-dpm... Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
