On Mon, Mar 04, 2019 at 03:12:40PM +0100, Antoine Jacoutot wrote:
> On Mon, Mar 04, 2019 at 03:04:22PM +0100, Marc Espie wrote:
> > On Mon, Mar 04, 2019 at 01:19:51AM +0100, Antoine Jacoutot wrote:
> > > On Sun, Mar 03, 2019 at 02:11:42PM +0000, Stuart Henderson wrote:
> > > > comments/ok?
> > >
> > > OK
> > > I wish we could somewhat automate this.
> >
> > More CONFIGURE_STYLE to get rid of more do-gen style targets would be
> > welcome. If you can find some standard order in which to run things,
> > such there are no special cases left, that would be really cool.
> >
> > I'll admit to having given up trying to read the autoconf manual.
>
> I think having a one-fits-all would be impossible.
>
> But having an autoreconf CONFIGURE_STYLE that would do something like this
> should take care of a lot of ports (definitely not all). *Not* saying it
> should
> be done this way, just providing an example to illustrate.
>
> AUTORECONF ?= autoreconf -fi
>
> BUILD_DEPENDS += ${MODGNU_AUTOMAKE_DEPENDS} \
> ${MODGNU_AUTOCONF_DEPENDS} \
> devel/libtool
>
> do-gen:
> cd ${WRKSRC} && env -i ${AUTOCONF_ENV} NOCONFIGURE=1 ${AUTORECONF}
>
>
> AUTORECONF could be set in the port Makefile to "autogen.sh" when needed.
Sounds like a plan. You probably want to write an actual patch and try it
out. :)
