On 2021-10-17 12:32 , Karl Berry wrote:
https://git.savannah.gnu.org/cgit/automake.git/commit/m4/python.m4?id=ed8daa069a6c8ed34f7856c42402ec46f305e670
However, this change leads to pkg-config .pc files containing the
variable name $PYTHON_PREFIX, not its content
I admit I didn't
On 2021-5-19 08:15 , Karl Berry wrote:
Hi Joshua and all - regarding https://bugs.gnu.org/35322, I have
(finally) pushed your patches. I tweaked the doc update a little bit and
created a new test to try out the --with-python_prefix and
--with-python_exec_prefix options. (I left the underscores in
On 2021-3-3 10:54 , Karl Berry wrote:
I wonder if it might also make sense to offer a configure option to set
PYTHON_PREFIX?
I think that would be great (--pythondir, --pythonexecdir or some
such). Would you mind looking into that? I've never played around with
the options Automake add
On 2021-3-6 10:26 , Karl Berry wrote:
Hi Joshua - did you run the full make check on your Mac?
I saw you patched some of the tests, which is great, so I'm guessing
you did, but just asking ...
On Jim's Mac system, many more tests (35) fail, but haven't tracked that
down yet. --thanks, karl.
I
On 2021-3-2 10:14 , Karl Berry wrote:
Thanks much for the patch (including fixing the tests). I don't see any
immediate comments. Jim and I will ponder for a couple days. --best, karl.
Thanks Karl. I'd certainly appreciate input from other packagers as well.
I wonder if it might also make sens
How about this? It bases the default values of PYTHON_PREFIX and
PYTHON_EXEC_PREFIX on sys.prefix and sys.exec_prefix respectively, which
the documentation has long said might happen. Behaviour should not
change in the case that sys.prefix = $prefix. The variables can still be
overridden; e.g.
On 2021-2-15 09:16 , Karl Berry wrote:
Unfortunately, simply removing the change to the `base' assignment as
you did in your change, for instance the first hunk,
-sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'})
+sitedir = sysconfig.get_path('purelib')
will affect
