For most of this year, @zwol and I have been working on a pretty ambitious project:
* to make a fresh release of GNU Autoconf, a crucial build tool that hadn't had a new release since 2012
* to get paid for that
* to help put Autoconf on a more sustainable footing so it doesn't have to get rescued again a little while down the road

Autoconf 2.70 is due out next month, and you can read my fresh LWN story about the rejuvenation & what's next:

@brainwane @zwol sounds interesting. I hope it won't break the compatibility with thousands of existing configs for older versions, though :)

@iron_bug Check the "2.70 does, unfortunately, include a few places where backward compatibility with 2.69 could not be preserved." section of the article. Definitely a good idea for folks to test the beta. @zwol

@iron_bug @brainwane @zwol well, 'testing the beta' if I build the whole system from sources and I use in general C/C++ software and have thousands of configs is a funny idea. but I wouldn't hurry up with such experiments, anyway.
but I gonna read the article, thanks.

@iron_bug @brainwane Debian has done that exact thing already and i'm crunching my way through the bugs. (if you have a lot of C++ i recommend you use dev trunk instead of 2.69c, there were some very important fixes for C++ that didn't quite make 2.69c)

@brainwane As a #GNU hacker & user: thanks a lot for undertaking this task!

@brainwane @zwol omg you make the amazing fiction posts on metafilter AND maintain critical internet infrastructure? 🤩

@zwol @brainwane typically true of LWN. i greatly appreciate their reporting and could do without about 90% of their commentariat.

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!