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. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
