> On 19 Feb 2022, at 5:06 pm, Gerben Wierda <gerben.wie...@rna.nl> wrote: > > Well, yes, I kind of knew already that it was a terrible idea. Kind of felt > terrible in the first place (was just checking). > > But how does one (a) find out the dependency exists and (b) make sure the > software finds python from MacPorts?
Not so easy, as it could be hidden away in the build infrastructure. It might
not be at all obvious from just looking at the port file...
Probably the only way is to wait for the bug reports once 12.3 is out ...
>
> G
>
> Sent from my iPhone
>
>> On 19 Feb 2022, at 17:26, Christopher Jones <jon...@hep.phy.cam.ac.uk> wrote:
>>
>>
>>
>>> On 19 Feb 2022, at 1:58 pm, Gerben Wierda via macports-dev
>>> <macports-dev@lists.macports.org> wrote:
>>>
>>> Oof.
>>>
>>> I’m happy to check as soon as 12.3 is out, but I wonder how to check.
>>> Installing a port is easy enough to do, but how do I find out if a port
>>> uses it in some arcane way? And if it does, how should one fix.
>>>
>>> I was wondering if a reasonable band-aid would be to have /usr/bin/python
>>> link to the one from MacPorts when installed, but given Apple’s strategy in
>>> clamping down, I guess that will not work in the long term, even if it
>>> might work in the short term. And of course, such a band-at only hides the
>>> debt that has now been created in the ports so it is a bad idea in other
>>> senses as well.
>>
>> Terrible idea all round. Don’t do it.
>>
>> Note /usr/bin/python3 is still there (for now). Ports that can use python3
>> instead could just use this, on the OSes that provide it.
>>
>> Better solution, as it works across more OSes, is to declare a dependency
>> (build, or lib depending on how python3 is used) on one of the macports
>> python3 versions and configure the builds to find that directly in ${prefix}.
>>
>> Chris
>>
>>
smime.p7s
Description: S/MIME cryptographic signature
