A new release would be great - it's very much needed. There are lots of missing features that distros have to work around with their own custom patches - 'runstatedir' most notably. These are causing CMake to gain ground, which maybe isn't great for those of us who love Autotools.
I don't think anybody wants Autoconf to become abandonware. Would it make sense to open up maintenance to new developers? On Tue, Mar 5, 2019 at 12:14 PM Tomasz Kłoczko <kloczko.tom...@gmail.com> wrote: > On Tue, 5 Mar 2019 at 19:00, Eric Blake <ebl...@redhat.com> wrote: > [..] > > > Is it any chance to make new release with what is already committed? > > > Where is the problem? Why so long no one was able to make a new > release? > > > > The problem, as always, is a lack of free time. > > So no one else want to continue autoconf maintenance and or no one can > do thsi by other reasons?? > > kloczek > PS. Old sentence says .. "if you need change the people .. you need > change the people" > -- > Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH > > _______________________________________________ > Autoconf mailing list > Autoconf@gnu.org > https://lists.gnu.org/mailman/listinfo/autoconf > _______________________________________________ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
