> It may be that libgc upstream's autogen.sh script is not really 'right' in > some way. But there may well be a lot of upstreams like that, which is > why maintainers need clear guidance on how to deal with this, without > having to become autotools experts. i.e how to determine when they can > just run dh_autoreconf and when they need to do something more > involved.
for example in my package hkl (I am also the upstream), the autogen.sh also run gtkdocize #!/bin/sh test -d m4 || mkdir m4 gtkdocize || exit 1 autoreconf -ivf -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/a2a20ec3b8560d408356cac2fc148e53b1e6e...@sun-dag3.synchrotron-soleil.fr
