Re: Running autogen.sh (was: Re: elinks upgrade request)

[Roland Illig <roland.illig%gmx.de@localhost>]

On 19.06.2020 20:11, Rhialto wrote:
> On Tue 16 Jun 2020 at 08:00:51 +0200, Roland Illig wrote:
> > I prefer to have the CONFIGURE_ENV set as well, resulting in:
> >
> > ${RUN} cd ${WRKSRC} \
> > && ${SETENV} ${CONFIGURE_ENV} ${CONFIG_SHELL} autogen.sh
> >
> > Since that line is quite long and I don't like to see that line
> > redundantly, each with tiny variations, I suggest that packages just define:
> >
> > HAS_AUTOGEN_SH= yes
> >
> > and the pkgsrc infrastructure takes care of the rest, running it in
> > pre-configure.
>
> Some versions of autogen.sh are not doing the same thing as other. I
> have seen many examples that end with running configure, and many that
> don't. Some do extra version checking on which autotools they accept.
>
> Some of these differences may be difficult to paper over. I am thinking
> in particular of the variant that automatically runs configure.

Exactly because of all these differences, someone (doesn't have to be
me) should run over all of the packages that currently run autogen.sh to
see what exactly these packages do and whether we can build a common
model that fits at least 95 percent of them.

The model I outlined above was the simplest that came to mind, by just
looking at the output of "grep -wr autogen .".  I'm sure that reality is
much more complicated than this.

Roland