It has been eight years since the release of autoconf 2.69, there’s
been substantial improvements checked into the development trunk since
then, and the mailing list regularly gets requests for a new release.
It is my understanding that the most important roadblock to a new
release is a lack of dev
Thanks for tackling this! Autoconf definitely needs a new release.
On Mon, Mar 9, 2020 at 2:23 PM Zack Weinberg wrote:
> It has been eight years since the release of autoconf 2.69, there’s
> been substantial improvements checked into the development trunk since
> then, and the mailing list regul
On Mon, 9 Mar 2020, Zack Weinberg wrote:
I’ve seen people suggest that there is a backlog of patches that have
been submitted to this mailing list but not reviewed, but considering
that there’s already more git commits in between 2.69 and now than
there were between 2.68 and 2.69, I think it wou
On 3/9/20 1:22 PM, Zack Weinberg wrote:
- Run the bundled testsuite (plain ‘make check’ only, not ‘make
distcheck’) on the following OS and CPU combinations, all of which
are readily accessible to me:
aarch64-unknown-linux-gnu
armhf-unknown-linux-gnu
mips64-unknown-linux-g
On 3/9/20 4:22 PM, Zack Weinberg wrote:
>
>I happen to know that these have particularly complicated configure
>scripts. I will also cheerfully take suggestions for additional
>packages to test in this manner.
>
Thanks for doing this. Two things might make Gentoo an attractive test
