On Wed, Mar 29, 2023 at 03:27:53PM +0200, Paolo Bonzini wrote:
> 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.
In a choice between 'shell configure' and 'python configure', I'll
take the python version, as it is a fundamentally better language to
be writing anything non-trivial in. My desire is to see the elimination
of as much shell code as possible. As a broad goal, python should be the
only scripting language we aim to use, in preference to shell or perl
or any equivalent.
I certainly prefer python to shell; I can try to move as much logic as I can into mkvenv.
For this RFC I tried to "disrupt" as little as I could so it was easier to see the through-line and gain a sense for what exactly was changing. If there's an appetite for being bolder and more aggressive, we can certainly do that. I'm going to work out the kinks for the baseline functionality first, then we can apply the lipstick.
Thanks,
(And sorry for the hiatus again. I haven't been feeling well, please forgive my spotty attention.)
--js