From: Christian Melki <christian.melki@t2data.com>
To: Ladislav Michl <oss-lists@triops.cz>
Cc: Michael Olbrich <m.olbrich@pengutronix.de>,
"ptxdist@pengutronix.de" <ptxdist@pengutronix.de>,
p.zabel@pengutronix.de
Subject: Re: [ptxdist] [PATCH 1/2] host-meson: version bump 0.61.4 -> 1.0.0
Date: Wed, 11 Jan 2023 12:20:30 +0100 [thread overview]
Message-ID: <30db325e-1637-a897-285c-0ed47e21bb59@t2data.com> (raw)
In-Reply-To: <Y76aWjg/vQXIUO0J@lenoch>
On 1/11/23 12:15, Ladislav Michl wrote:
> On Wed, Jan 11, 2023 at 12:02:54PM +0100, Christian Melki wrote:
>> On 1/11/23 11:19, Philipp Zabel wrote:
>>> https://mesonbuild.com/Release-notes-for-1-0-0.html
>>>
>>> This bumps the host Python minimum version requirement from 3.6 to 3.7.
>>
>> Highly subjective disclaimer here,
>>
>> This boils down to when ptxdist starts forcing users to python 3.7+ for
>> building. Calling python (as a build tool) outdated when the last 3.6.x
>> release was in late 2021, is a stretch.
>> I'm pro upgrade, but also really dislike breaking stuff like this.
>
> python3 package, therefore host-python as well is already at 3.10.4,
> so it does not make any difference.
>
I don't follow.
I'm talking about host-meson requires host-system-python3.
> l.
next prev parent reply other threads:[~2023-01-11 11:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 10:19 Philipp Zabel
2023-01-11 10:19 ` [ptxdist] [PATCH 2/2] pre/Rules.make: let Meson generate relocatable .pc files Philipp Zabel
2023-02-08 11:49 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-01-11 11:02 ` [ptxdist] [PATCH 1/2] host-meson: version bump 0.61.4 -> 1.0.0 Christian Melki
2023-01-11 11:15 ` Ladislav Michl
2023-01-11 11:20 ` Christian Melki [this message]
2023-01-11 11:20 ` Michael Olbrich
2023-01-11 13:14 ` Ladislav Michl
2023-01-11 11:17 ` Michael Olbrich
2023-02-08 11:49 ` [ptxdist] [APPLIED] " Michael Olbrich
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=30db325e-1637-a897-285c-0ed47e21bb59@t2data.com \
--to=christian.melki@t2data.com \
--cc=m.olbrich@pengutronix.de \
--cc=oss-lists@triops.cz \
--cc=p.zabel@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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