autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Any chance to make a new autoconf release?


From: bill-auger
Subject: Re: Any chance to make a new autoconf release?
Date: Tue, 5 Mar 2019 15:15:13 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Iceape/2.49.2

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 <address@hidden> wrote:
>> 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??

eric did not imply that he did not want to continue

autoconf is a GNU project - that means anyone can, and is encouraged, to
contribute


Tomasz Kłoczko wrote:
> you need change the people"

is that a volunteer offer?
do you have more free time than eric?
great - please do contribute, or perhaps recommend someone who can

free software, like any volunteer work, is not an obligation of any
volunteer; nor is it an entitlement of any beneficiary such as software
users - it is a labor of love, and a dialog between developers and users
- if some project is not getting as much love as is needs, it is
incumbent upon it's users every bit as much as it's developers to give
it some love, or find someone who can

in this case, the only flaw you mentioned is that tests are failing; but
is there any functionality that is broken? - that would be a much more
critical concern - have you reported any bugs regrading essential
functionality that you need but are broken? - perhaps it is only the
tests are broken


Tomasz Kłoczko wrote:
> In current situation even if something still is not finished it wold
> be better to release what is  now in git.

that would not be better - a standard development tool like this needs
to be stable, versioned, well documented, etc; otherwise you can not
expect that anyone who receives your source code will be able to build
it, unless they resort to using what would be an experimental
pre-release build tool - most would not consider that better; but a
last-resort compromise

of course, a broken build tool is not great either; but is it broken? -
that would be the important thing to discuss

Attachment: pEpkey.asc
Description: application/pgp-keys


reply via email to

[Prev in Thread] Current Thread [Next in Thread]