On Wed, 2012-06-06 at 00:33:10 +0200, Carsten Hey wrote:
> * Guillem Jover [2012-06-05 11:12 +0200]:
> > > (a configure script would ease testing patches)
> >
> > I'm not sure what you mean with this?
>
> I did not write what I meant ;)
Ok. :)
> What I meant is that it is not obvious without looking into the
> documentation that autoreconf -f -i is the correct way to generate
> a configure script. For regular contributors this is not a problem, but
> if one only plans to send one patch, making this more obvious would ease
> doing so.
JFYI, dpkg-buildpackage/debuild would have taken care of that too.
> For example, a autogen.sh in the repositories root directory with the
> content below would have made it obvious for me:
>
> #/bin/sh
> autoreconf -f -i
Well, I guess I always assume that if there's a configure.{in,ac}
«autoreconf -f -i» should work, and only if there's an autogen{,.sh}
then that means some special handling is needed. Otherwise the source
needs fixing anyway, IMO. :)
regards,
guillem
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
