Hello Matt, others, On Mon 13 Jan 2020 at 02:05PM -08, Matt Taggart wrote:
> I am working on creating a new package and I have chosen use the > 'dgit-maint-merge' method of packaging (see dgit-maint-merge(7) in the > dgit package). > > This method (and some of the other dgit(1) recommended methods) > generates the initial packaging out of a checked out git repository, > rather than an unpacked upstream tarball in a versioned directory and > orig tarball. I have only ever used debmake to generate the contents of debian/, after I've already got the upstream source into git myself. Are you asking for debmake to do that for you if you provide it with an upstream git repo clone URI? On Mon 13 Jan 2020 at 04:10PM -08, Matt Taggart wrote: > I also realized for dgit-maint-merge debhelper might want to do the > following differently: s/debhelper/debmake/ right? > 1) don't create debian/patches/ > > 2) don't create debian/source/local-options > > 3) I'm not sure if watch is needed > > 4) create debian/source/options containing: > single-debian-patch > auto-commit > > 5) create debian/source/patch-header with a description of how to get > changes to the upstream source. I guess this should be a template that > fills in package name and git repo? > > For #3 and #4 see the dgit-maint-merge(7) manpage for examples and > explanation. I think that debmake might not be the right place for (2), (4) and (5). Instead, I think a 'maintmerge' script in the dgit package should do that setup, so that non-debmake users can take advantage. See #852226. -- Sean Whitton
signature.asc
Description: PGP signature
