Discussion:
Bug#948844: debmake: option for git maintained packages
(too old to reply)
Matt Taggart
2020-01-13 22:10:02 UTC
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
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
Sean Whitton
2020-01-25 17:40:02 UTC
Permalink
Hello Matt, others,
Post by Matt Taggart
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?
Post by Matt Taggart
I also realized for dgit-maint-merge debhelper might want to do the
s/debhelper/debmake/ right?
Post by Matt Taggart
1) don't create debian/patches/
2) don't create debian/source/local-options
3) I'm not sure if watch is needed
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
Matt Taggart
2020-01-26 00:10:02 UTC
Permalink
Post by Sean Whitton
Hello Matt, others,
Post by Matt Taggart
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?
I am following the the "When upstream tags releases in git" section of
dgit-maint-merge(7) and when I get to the "Now go ahead and
Debianise..." section I'd like to be able to run debmake, but it's
expecting the source dir to have a particular name and the orig tarball
to exist.
Post by Sean Whitton
s/debhelper/debmake/ right?
Yes, sorry.
Post by Sean Whitton
Post by Matt Taggart
1) don't create debian/patches/
2) don't create debian/source/local-options
3) I'm not sure if watch is needed
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.
debmake is already creating a template for (2).
I like the idea of putting these steps in a dgit script though and
having the dgit-maint-merge(7) manpage explain how to use it. Then maybe
debmake could add a basic mode to handle the other remaining things.
--
Matt Taggart
***@debian.org
Loading...