Ah, got it. Fix pushed. Thanks.
I also finally figured out the cause of "pyenv: pip: command not found" and
pushed a fix for that too.
BTW, I don't see ~/.pythonversion. Are you sure that's from pyenv?
Regards,
John Ralls
> On Feb 15, 2022, at 2:08 PM, Spock wrote:
>
> Sorry - I did not expl
Sorry - I did not explain myself well enough there John.
I guess the issue that I’m pointing out is that gtk-osx-setup.sh writes the
jhbuild script but writes an absolute path for $PATH to be set to rather than
escaping so that $PATH is read from the environment when running jhbuild.
In the cod
Well, it's been a requirement since forever that you put $DEVPREFIX/bin in your
path before invoking jhbuild, but I suppose there's no harm in also adding it
with jhbuild to prevent path pollution. I hadn't noticed ~/.pythonversion.
That's rude of them, I'll look for a way to bury that somewhere
Hi John,
I guess the issue with the $PYENV local 23.10.0 is that it causes
~/.pythonversion to be created - which may or may not be a permanent change a
developer might want?
The more serious issue is with meson not finding ninja. I think this is down to
jhbuild not having ~/.new_local/bin in
