Hi,
It is almost 7 years since last time autoconf have bee released.
It is a lot well known issues and almost half of the test suite is
failing because many software components moved forward.
Is it any chance to make new release with what is already committed?
Where is the problem? Why so long no
On 3/5/19 12:11 PM, Tomasz Kłoczko wrote:
Hi,
It is almost 7 years since last time autoconf have bee released.
It is a lot well known issues and almost half of the test suite is
failing because many software components moved forward.
Is it any chance to make new release with what is already com
On Tue, 5 Mar 2019 at 19:00, Eric Blake 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 ma
i dont have the answer you are hoping for, Tomasz; but i would like to
point out a few things about this message
Tomasz Kłoczko wrote:
> On Tue, 5 Mar 2019 at 19:00, Eric Blake wrote:
>> The problem, as always, is a lack of free time.
>
> So no one else want to continue autoconf maintenance and
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 an
Nicholas Clark wrote:
> Would it make
> sense to open up maintenance to new developers?
i hope im not wrong about that, but i quite assume that because it is a
GNU project, that strongly implies that contributions are welcome from
everyone, and if the current maintainers need help, that they are f
On Tue, 5 Mar 2019, Nicholas Clark wrote:
I don't think anybody wants Autoconf to become abandonware. Would it make
sense to open up maintenance to new developers?
The project has always been open to new developers.
Please do not feel discouraged from volunteering all of your available
time
So let's say somebody from the community wanted to cut a new Autoconf
release. How would they go about doing it?
On Tue, Mar 5, 2019 at 1:47 PM Bob Friesenhahn
wrote:
> On Tue, 5 Mar 2019, Nicholas Clark wrote:
>
> > I don't think anybody wants Autoconf to become abandonware. Would it make
> > s
On 3/5/19 3:01 PM, Nicholas Clark wrote:
> So let's say somebody from the community wanted to cut a new Autoconf
> release. How would they go about doing it?
HACKING gives a nice overview, but a good first hurdle to clear is to at
least prove that you are capable of submitting patches (such as a p
On Tue, 2019-03-05 at 15:06 -0600, Eric Blake wrote:
> On 3/5/19 3:01 PM, Nicholas Clark wrote:
> > So let's say somebody from the community wanted to cut a new Autoconf
> > release. How would they go about doing it?
>
> HACKING gives a nice overview
One hurdle that people may want to keep in min
On 3/5/19 11:00 AM, Eric Blake wrote:
>
> The problem, as always, is a lack of free time.
>
> I'm hoping to spend some of my $DAYJOB time on getting a release out
> the door, but am still waiting approval on that front
How about if I turn the crank and release what's in master now? That is,
I run
11 matches
Mail list logo
