On 20/08/24 11:07, Matthias Klose wrote:
On 20.08.24 10:09, Gioele Barabucci wrote:
Control: tags -1 - wontfix
On 20/08/24 09:57, Matthias Klose wrote:
Control: tags -1 + wontfix
For packages doing more than one build, I consider the sequencer a
complicator, not a helper.
Hi,
maybe you have misinterpreted the patch. As you can see comparing
[1] https://salsa.debian.org/gioele/bash/-/blob/0e52fc/debian/rules
to
[2] https://salsa.debian.org/gioele/bash/-/blob/fc131d/debian/rules
the version with the standard sequence [1] is shorter (5 KB vs 13 KB!)
and easier to understand. (And produces bit-identical results.) (And
could be further simplified by dropping the need to produce bit-
identical packages.)
Based on what do you classify the version with the standard sequence
as more complex?
it's a pita to restart a partially failed build in the target where it
failed. yes, this is more complex with the sequencer.
How is that different? One can still call the individual targets of
d/rules or the single target handlers like "dh_auto_build
--builddirectory=foo".
BTW, the build is now much much faster.
The standard sequence + compat 13 enable parallel builds. sbuild logs
tell me that a full package build with `gbp buildpackage` (with <nodoc>
and <nocheck>) takes about a minute (most of which spent waiting for
autoconf).
Doing full build in sbuild is now faster than resuming partial builds
using the non-standard d/rules file.
I built the package ~400 times to complete the conversion (including the
no-doc and rrr-no patchsets), with plenty of errors in the middle of the
build process. My experience is that once I reached a point in which dh
(= standard sequence) was the main driver, I could iterate much faster.
Regards,
--
Gioele Barabucci
