If anyone who weighed in on the Python prefix stuff (or didn't, for that
matter) has a chance to try the new pretest at
https://meyering.net/automake/automake-1.16g.tar.xz
that'd be great. It'd be nice not to have to do another patch-up release.
Thanks,
Karl
Regarding PYTHON_PREFIX setting in automake, I've pushed a change that
(I hope) reverts to the previous behavior of using the usual GNU prefix
variables by default. It's attached.
The new configure option --with-python-sys-prefix yields the
the 1.16.4 behavior of using the sys.* Python values.
I think we need an easy way to set a default for this behaviour
from within configure.ac, similar to AC_PREFIX_DEFAULT(), so that
the end-user doesn't have to pass a bunch of options to configure
just to get the build to work sensibly.
I have nothing against the idea, but my
On 21-08-25 10:00, Karl Berry wrote:
| yf> Would keeping PYTHON_PREFIX but changing its default to the
| "classical" value be a working solution for this ?
|
| Yes, I think we should. And I think I should have been smart enough to
| realize that changing the default behavior was
yf> Would keeping PYTHON_PREFIX but changing its default to the
"classical" value be a working solution for this ?
Yes, I think we should. And I think I should have been smart enough to
realize that changing the default behavior was too risky in the first
place. Apologies for that.
My
On 2021-8-25 10:14 , Karl Berry wrote:
Ok, I guess we'll have to revert the Python change and make another
release. I was worried about the change. But I am not sure of how best
to deal with the intended benefits.
Joshua, can you please take a look at these reports and advise?
Hello,
Would keeping PYTHON_PREFIX but changing its default to the "classical" value
be a working solution for this ?
Best regards,
Yvan
Le 25 août 2021 07:08, j...@macports.org a écrit :
On 2021-8-25 10:14 , Karl Berry wrote:
> Ok, I guess we'll have to revert the Python change and make
Ok, I guess we'll have to revert the Python change and make another
release. I was worried about the change. But I am not sure of how best
to deal with the intended benefits.
Joshua, can you please take a look at these reports and advise?
Hello,
I concurr.
In the case of the software I work on (code-saturne.org), we have in addition
chosen not to version generated files, so as to be more consistent with a
"maintainer mode" logic. Meaning that depending on the machine we install on,
we can get a different behavior, as we cannot
