From: Patrick Steinhardt <ps@pks•im>
To: Renato Botelho <garga@FreeBSD•org>
Cc: Ramsay Jones <ramsay@ramsayjones•plus.com>,
Junio C Hamano <gitster@pobox•com>,
GIT Mailing-list <git@vger•kernel.org>
Subject: Re: Bug: build is broken on FreeBSD if libsysinfo is installed
Date: Thu, 3 Jul 2025 15:02:20 +0200 [thread overview]
Message-ID: <aGZ_XEJrZkv83QyR@pks.im> (raw)
In-Reply-To: <90f5ae50-51a5-4188-b76e-90ab2621551c@FreeBSD.org>
On Thu, Jul 03, 2025 at 09:35:47AM -0300, Renato Botelho wrote:
> On 03/07/25 05:40, Patrick Steinhardt wrote:
> > There are no plans to remove our Makefile right now, but there is intent
> > to remove autotools once Meson reaches feature parity with our Makefile.
> > It will probably still be a couple releases before that happens, and we
> > of course still have to make the final decision to actually go through
> > with the removal. But it likely is to happen in the not-too-distant
> > future.
>
> Thank you for the explanation. I'll keep an eye on the announcements and as
> soon as meson is considered "feature-complete" I'll start experimenting with
> it on FreeBSD ports to be ready to flip the switch when the time comes.
Thanks, that would be highly appreciated. The more testing we get from
different platforms the more solid it becomes :)
Patrick
next prev parent reply other threads:[~2025-07-03 13:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 14:09 Bug: build is broken on FreeBSD if libsysinfo is installed Renato Botelho
2025-07-01 16:05 ` Renato Botelho
2025-07-01 20:03 ` Eric Sunshine
2025-07-01 20:03 ` Ramsay Jones
2025-07-02 11:28 ` Renato Botelho
2025-07-02 17:08 ` Junio C Hamano
2025-07-02 19:48 ` Renato Botelho
2025-07-02 22:37 ` Ramsay Jones
2025-07-02 23:08 ` Junio C Hamano
2025-07-02 22:33 ` Ramsay Jones
2025-07-03 8:40 ` Patrick Steinhardt
2025-07-03 12:35 ` Renato Botelho
2025-07-03 13:02 ` Patrick Steinhardt [this message]
2025-07-02 18:32 ` Eli Schwartz
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=aGZ_XEJrZkv83QyR@pks.im \
--to=ps@pks$(echo .)im \
--cc=garga@FreeBSD$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=ramsay@ramsayjones$(echo .)plus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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