From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"John Snow" <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Subject: Re: [RFC PATCH 3/3] configure: install meson to a python virtual environment
Date: Wed, 29 Mar 2023 15:27:53 +0200 [thread overview]
Message-ID: <88e77761-e9fe-d473-a4fa-c1d553bff4f3@redhat.com> (raw)
In-Reply-To: <ZCQ0x3cDXOUsSX76@redhat.com>
On 3/29/23 14:53, Daniel P. Berrangé wrote:
> I would love to see a day where configure isn't involved in the
> build process. Obviously we can't put this new logic into
> meson as its a chicken & egg problem. Could we potentially
> have your new python/scripts/mkvenv.py script be responsible
> for setting up meson in the venv though, so we can avoid
> adding more shell code to configure ?
Not sure this is the same thing a what you want, but I do have a
pipedream of rewriting configure in Python. At this point it has a lot
more logic than it has command invocations.
John, do you think it makes sense to do the "pip install" steps already
in mkvenv's post_post_setup phase? Maybe by passing a version spec like
meson>=0.61.5 in place of the simpler "--gen pip,meson,sphinx" that you
have now?
Not for this series; just dumping some thoughts prompted by Daniel's
question.
Paolo
next prev parent reply other threads:[~2023-03-29 13:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 21:11 [RFC PATCH 0/3] configure: create a python venv and install meson John Snow
2023-03-28 21:11 ` [RFC PATCH 1/3] python: add mkvenv.py John Snow
2023-03-29 12:56 ` Paolo Bonzini
2023-03-30 14:00 ` John Snow
2023-03-31 8:44 ` Paolo Bonzini
2023-03-31 10:01 ` Paolo Bonzini
2023-04-13 16:10 ` John Snow
2023-04-13 16:26 ` John Snow
2023-03-28 21:11 ` [RFC PATCH 2/3] tests: add python3-venv dependency John Snow
2023-03-28 21:11 ` [RFC PATCH 3/3] configure: install meson to a python virtual environment John Snow
2023-03-29 12:32 ` Paolo Bonzini
2023-03-29 12:53 ` Daniel P. Berrangé
2023-03-29 13:27 ` Paolo Bonzini [this message]
2023-03-29 13:31 ` Daniel P. Berrangé
2023-04-12 1:27 ` John Snow
2023-03-29 13:02 ` [RFC PATCH 0/3] configure: create a python venv and install meson Paolo Bonzini
2023-03-30 14:11 ` John Snow
2023-03-31 8:40 ` Paolo Bonzini
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=88e77761-e9fe-d473-a4fa-c1d553bff4f3@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).