Recommendation: adopt git-dpm
I've done enough experimentation to feel confident in my opinion that the team should adopt git-dpm as its git packaging regime. Note that this is just my personal opinion. I look forward to feedback from other team members and interested parties, either for or against my recommendation. I've only considered git-dpm and gbp-pq since the other technologies (e.g. dgit + git-debcherry) don't seem to be viable right now in unstable. git-debcherry in particular does not seem to be part of the released gitpkg package (although it's in upstream's git repo). Both git-dpm and gbp-pq have discomforts, and I would consider contributing to either project to help smooth out some edges. Despite those, git-dpm seems like the best workflow, the easiest to describe and comprehend, and the more robust of the regimes. IMHO, git-dpm's downsides are: its tag names (I prefer them with slashes), some minor missing features (import-dscs command and --uscan option), and the fact that it's written in shell. I'm fairly comfortable with shell hacking, but take a look at git-dpm and tell me that doesn't just scream for a more comprehensible re-implementation in Python 3. :) Even with those complaints, git-dpm feels like the better tool for team package management in git. The problems are minor and probably easily fixable. I look forward to other opinions. Cheers, -Barry signature.asc Description: PGP signature
Re: Recommendation: adopt git-dpm
On Thu, 04 Sep 2014, Barry Warsaw wrote: Even with those complaints, git-dpm feels like the better tool for team package management in git. The problems are minor and probably easily fixable. From my point of view, since you're anyway using features of git-buildpackage, it would be better to improve git-buildpackage... I like how git-dpm can keep patches applied on the packaging branch and porting the required shell to gbp pq should not be too complicated. It would also be nice if we could fix gbp pq to not rename quilt patches. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- 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/20140904223231.gb7...@x230-buxy.home.ouaza.com
Re: Recommendation: adopt git-dpm
On Sep 05, 2014, at 12:32 AM, Raphael Hertzog wrote: From my point of view, since you're anyway using features of git-buildpackage, it would be better to improve git-buildpackage... I like how git-dpm can keep patches applied on the packaging branch and porting the required shell to gbp pq should not be too complicated. It would also be nice if we could fix gbp pq to not rename quilt patches. Maybe. What I thankfully left out of my description was the dozen gbp-pq directories I had to trash when I tried to do something that *seemed* to make sense but ended up just borking my directory. Sometimes I could chuck the changes and try again, but more often than not, I just rmdir'd and started over. Even after getting it right (and updating my draft), I still don't feel like gbp-pq is very resilient. I wrote the git-dpm bits after just one or two such experiments. Either way, I think we need better focused task-oriented documentation! Cheers, -Barry -- 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/20140904184310.0c4a5...@anarchist.wooz.org
