On Sat, Apr 19, 2014 at 06:42:27AM +0000, PICCA Frederic-Emmanuel wrote:
> > 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
That's Bug#640376. It seems that doing
+
+# Run gtkdocize automatically
+if (-f "/usr/bin/gtkdocize" and not @ARGV) {
+ my $configure = (-e "configure.ac") ? "configure.ac" : "configure.in";
+
+ if (-e $configure && grep(/^GTK_DOC_CHECK/, readfile($configure))) {
+ doit("gtkdocize", "--copy");
+ }
would fix the issue in most cases (except for sub-directories). I could
do this recursively, but I'm not sure that's the best solution for this
problem.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Please do not top-post if possible.
--
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/20140422202550.GC15264@jak-x230
