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
