public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] Makefile: deprecate autoconf build infrastructure
Date: Wed, 04 Mar 2026 10:10:50 -0800	[thread overview]
Message-ID: <xmqq8qc78nyt.fsf@gitster.g> (raw)
In-Reply-To: <20260304-pks-autoconf-deprecation-v1-0-f5b611b13138@pks.im> (Patrick Steinhardt's message of "Wed, 04 Mar 2026 09:22:59 +0100")

Patrick Steinhardt <ps@pks.im> writes:

> roundabout 1.5 years ago we had a long discussion that eventually led to
> a rough consensus that we'd rather want to get rid of our autoconf build
> infrastucture. This eventually led to the introduction of Meson to cover
> this use case, which has stabilized for quite a while by now.
>
> This patch series thus starts the deprecation period of the autoconf
> build infrastructure. Target for removal is Git 2.55 for now, but I'm
> very open for discussions here. I also assume that depending on feedback
> from packagers we may need to adapt the timeline.

I do not consider autoconf a thing on its own; rather it is a mere
extension to Makefile based build, isn't it?  So the declaration to
say "we favor meson over autoconf" makes little sense, at least to
me.

Asking which between Makefile and Meson should be the "primary"
build environment is a different story, and the question does make
sense, even though my answer may be different from yours ;-)

  parent reply	other threads:[~2026-03-04 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  8:22 [PATCH RFC 0/2] Makefile: deprecate autoconf build infrastructure Patrick Steinhardt
2026-03-04  8:23 ` [PATCH RFC 1/2] INSTALL: recommend Meson instead of autoconf Patrick Steinhardt
2026-03-04  8:23 ` [PATCH RFC 2/2] Makefile: deprecate autoconf build infrastructure Patrick Steinhardt
2026-03-04 18:10 ` Junio C Hamano [this message]
2026-03-11  7:51   ` [PATCH RFC 0/2] " Patrick Steinhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq8qc78nyt.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox