Hi Sebastian.

On 29/1/25 06:41, Sebastian Andrzej Siewior wrote:
I plan to switch to cmake at some point. Then we don't have to worry
about autoconf magic.
Sounds good.
    override_dh_update_autotools_config:
         ./autogen.sh
How is this different from the current autoreconf step that is already
as part of dh? Note that problem back then was that the shipped archived
contained m4 files so the autogen step did not "help".

The default update autotools dh rule doesn't seem to work / produce the same result without the autogen assets already present in the package source.

I don't know what you want me to do here. Other than adding ./autogen.sh
as part of the build process which is already handled.


I'm simply suggesting using the Github source as the upstream not the Github release tarball.

Regards,

Sam.

Reply via email to