Hello, On Sun 19 May 2019 at 11:24pm +0100, Ian Jackson wrote:
> Shengjing Zhu writes ("Bug#903392: want support for packaging-only maintainer
> views"):
>> Here's the example for my package, which only has debian dir in
>> debian-branch.
>>
>> https://salsa.debian.org/zhsj-guest/anbox
>>
> [...]
>
> I observe that in your git repository there is a tag
> upstream/0.0_git20190124
> and that this tag
> (i) appears to contain the upstream git history
> (ii) is absolutely identical to your orig tarball
> anbox_0.0~git20190124.orig.tar.gz
> I think you must have generated the latter with git-deborig or
> something. This is good.
>
>
> I intend to support this with
> --quilt=packaging-git
>
> Sean, there is of course the other possibility, where upstream is only
> a tarball. I propose to intend to support this, eventually, with
> --quilt=packaging-plus-tar
I think that for workflows where only debian/ is checked into git, not
having the upstream git history is probably more common than Shengjing's
case of having an upstream/foo tag.
Thus, I suggest that we use the shorter names --quilt=packaging for the
tarballs-only case, and --quilt=packaging-git for Shengjing's workflow.
An alternative to 'packaging' would be 'debiandir'.
> dgit will look for the corresponding upstream source tag with an
> algorithm like git-deborig's. In case that doesn't work there will
> have to be an option to specify it explicitly.
I think this is right.
The user's first step is to independently select a --quilt option (to
keep typing, or to put in .git/config), which they should always be able
to do, as they know what workflow they intend to use.
Then any additional information dgit can't figure out for itself can be
optional arguments.
--
Sean Whitton
signature.asc
Description: PGP signature
