Discussion:
Bug#948844: debmake: option for git maintained packages
Add Reply
Matt Taggart
2020-01-13 22:10:02 UTC
Reply
Permalink
Package: debmake
Version: 4.3.1-1
Severity: wishlist

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 would like debmake to have an option to support this method and just
setup the debian directory with the templates filled in. Maybe such an
option would require -p and -u to get the package name and version since
it might not be able to determine them from the directory/tarball, that
would be OK I think. It might also not be able to distinguish between
debian native and upstream packages either, so might default to upstream
unless -n is specified.

What do you think?

Thanks,
--
Matt Taggart
***@debian.org
Matt Taggart
2020-01-14 00:20:02 UTC
Reply
Permalink
I also realized for dgit-maint-merge debhelper might want to do the
following differently:

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.
--
Matt Taggart
***@debian.org
Loading...