automake
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: automake 1.16.4 and new PYTHON_PREFIX


From: FOURNIER Yvan
Subject: Re: automake 1.16.4 and new PYTHON_PREFIX
Date: Wed, 25 Aug 2021 06:40:41 +0000

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, jmr@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 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?
> https://lists.gnu.org/archive/html/automake/2021-08/msg00007.html
> https://lists.gnu.org/archive/html/automake/2021-08/msg00006.html

I guess the fundamental question is: Why are we asking python where it
wants modules installed? If it's so we can install modules in a place
where python will find them, it makes sense that $PYTHON_PREFIX may be
distinct from $prefix. If it's so that we can install modules in a
consistent subdir relative to the prefix, then we run into the problem
that what python gives you is not always relative to the prefix (and
isn't necessarily consistent). It seems like using a fixed subdir would
solve that problem better than asking python.

If reliance on the previous behaviour is widespread enough that the
change is unacceptable, some alternatives might be to have different
behaviour depending on whether the discovered python is in the
configured prefix or not, or depending on whether or not python is a
framework build. The downside is more special cases and more potential
for confusion.

Whatever else you decide to do, please keep the --with-python_prefix
option. Having that makes it at least possible to install in the right
place for framework builds, even if the defaults go back to being
incorrect for that case.

- Josh



Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à 
l'intention exclusive des destinataires et les informations qui y figurent sont 
strictement confidentielles. Toute utilisation de ce Message non conforme à sa 
destination, toute diffusion ou toute publication totale ou partielle, est 
interdite sauf autorisation expresse.

Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le 
copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si 
vous avez reçu ce Message par erreur, merci de le supprimer de votre système, 
ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support 
que ce soit. Nous vous remercions également d'en avertir immédiatement 
l'expéditeur par retour du message.

Il est impossible de garantir que les communications par messagerie 
électronique arrivent en temps utile, sont sécurisées ou dénuées de toute 
erreur ou virus.
____________________________________________________

This message and any attachments (the 'Message') are intended solely for the 
addressees. The information contained in this Message is confidential. Any use 
of information contained in this Message not in accord with its purpose, any 
dissemination or disclosure, either whole or partial, is prohibited except 
formal approval.

If you are not the addressee, you may not copy, forward, disclose or use any 
part of it. If you have received this message in error, please delete it and 
all copies from your system and notify the sender immediately by return message.

E-mail communication cannot be guaranteed to be timely secure, error or 
virus-free.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]