Re: Getting rid of 1.0 with dpatch/quilt/direct changes
On 2021-04-08 18:02 +0200, Mattia Rizzolo wrote:
> On Thu, Apr 08, 2021 at 03:53:06PM +0000, Holger Levsen wrote:
>> On Thu, Apr 08, 2021 at 02:58:14PM +0200, Lucas Nussbaum wrote:
>> > 166 1.0, quilt
>>
>> I don't see what's wrong with these.
>
> Nothing *wrong* as the hard meaning of that word.
> But:
> * They carry the usual set of downsides of 1.0 vs 3.0, like:
> - no support for .tar.(bz2|xz|…)
> - no support for multi tarballs
> * possibility of bugs due to the implementations of the patch/unpatch
> routines in d/rules
> * also similar to the above, you can't assume the state of the
> unpacked source (patched or unpatched?)
> * they are different from no good reason (0.5% vs 94.8%), and
> consistency in complex setup carry some good points by itself
>
> And at the same time I can't really think of any good point of keeping
> them 1.0.
>
>
> IMHO, they aren't "wrong" or "inherently bad", but I believe keeping
> them that way is more of technical debt than anything else.
The X Strike Force is still sticking to format 1.0, with one of the main
reasons being that it makes it easier to cherry-pick one or several
upstream commits. In the 3.0 format you have to create a separate patch
and later remove it when merging in the next upstream version.
Whether this outweighs the disadvantages of the 1.0 format is debatable,
but I think it would be best to start a discussion on the debian-x list
or the #debian-x IRC channel before filing individual bugs.
Cheers,
Sven
Reply to: