On Wed, 2021-01-20 at 17:15 -0500, Zack Weinberg wrote:
> As a starting point, I wrote up a "strengths, weaknesses,
> opportunities, and threats" analysis for Autotools -- this is a
> standard project management technique, if you're not familiar with
> it, there's a nice writeup in the draft of
* On 2021 20 Jan 17:33 -0600, Bob Friesenhahn wrote:
> Autotools is in great danger of becoming irrelevant, at least for new
> software development. A lot of people feel hostile toward it.
This is quite true.
As a co-maintainer of a library project that uses Autoconf, Automake,
and Libtool,
It seems better not to start another language. with already lack of
resources, that will further dilate available resources, and hard to
compete with other tools already us9ng Python's mature ecosystem
On Wed, Jan 20, 2021 at 3:32 PM Bob Friesenhahn <
bfrie...@simple.dallas.tx.us> wrote:
>
> In
On Wed, 20 Jan 2021, Zack Weinberg wrote:
Now we've all had a while to recover from the long-awaited Autoconf
2.70 release, I'd like to start a conversation about where the
Autotools in general might be going in the future. Clearly any future
development depends on finding people who will do
Thanks for writing all of this.
I'm writing from the perspective of a long-term user of the autotools.
A discussion like the one you have started will likely attract many
opinions. Some will be contradictory. However, somebody in the end
will have to decide.
The challenge seems to be to evolve
Now we've all had a while to recover from the long-awaited Autoconf
2.70 release, I'd like to start a conversation about where the
Autotools in general might be going in the future. Clearly any future
development depends on finding people who will do the work, but before
we worry about that I
