Hello, On Wed 22 Feb 2023 at 09:45PM GMT, Ian Jackson wrote:
> Sean Whitton writes ("Bug#1031793: dgit: Treat single-debian-patch as
> implying --quilt=single"):
>> How about having single-debian-patch imply --quilt=single in the absence
>> of any other setting or command line argument for the quilt mode?
>> Then in the docs we would say that it is a good idea to use only the git
>> configuration value, but that this is another option if you prefer it.
>>
>> This is still better than the previous situation because dgit will undo
>> some problems created by single-debian-patch (right?).
>
> The usual reason for eschewing in-tree directions about quilt format
> is that the tree can't (mustn't) tell you if it's patches-applied or
> not. I think it would be OK for the tree to influence *how* patches
> are made (ie, choose between --quilt=linear, --quilt=single, etc.)
Yes, this is a good distinction.
> There is also the fact that it would have an effect on dgit's
> behaviour for an NMUer, but I think that's OK for this.
>
> So your idea has merit.
>
> However, do we want to have people put single-debian-patch in the
> source tree ? That has such weird dpkg-source behaviours.
Right, but the pile of Emacs addons I maintain using dgit-maint-merge(7)
will never hit any of those behaviours. So it's a high cost to impose
on someone in a position such as mine.
> Ideally we would do something that would influence dgit, but not
> dpkg-source. So maybe we could put some *other* dropping in the
> source tree?
I'm reluctant to introduce something else like this when we already have
the git-debpush tags thing. Hmm -- is there some reason why dgit
couldn't put information in those tags in the same way?
--
Sean Whitton
signature.asc
Description: PGP signature
