It has been announced that /usr/bin/python will be removed in macOS 12.3, of
which a beta is already out.
If you have ports that use /usr/bin/python, please ensure that at minimum they
are switched to use MacPorts python27 on macOS 12 and later. Better yet, see if
you can switch them to use a
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
> On 19 Feb 2022, at 1:58 pm, Gerben Wierda via macports-dev
> 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.
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?
G
Sent from my iPhone
> On 19 Feb 2022, at 17:26, Christo
> On 19 Feb 2022, at 5:06 pm, Gerben Wierda 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 MacP
On Sat, Feb 19, 2022 at 05:23:41PM +, Christopher Jones wrote:
> > 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 j
> On Sat, Feb 19, 2022 at 05:23:41PM +, Christopher Jones wrote:
>>> But how does one (a) find out the dependency exists and (b) make
>>> sure the software finds python from MacPorts?
Lots of ports take the obvious approach of simply creating a symlink or
“python3" to MacPorts’s Python in,
On Feb 19, 2022, at 11:06, Gerben Wierda wrote:
> But how does one (a) find out the dependency exists and (b) make sure the
> software finds python from MacPorts?
General-purpose answers to either question are not possible. Each affected port
will need to be investigated and fixed in its own un
> On 21 Feb 2022, at 17:06, Ryan Schmidt wrote:
>
> On Feb 19, 2022, at 11:06, Gerben Wierda wrote:
>
>> But how does one (a) find out the dependency exists and (b) make sure the
>> software finds python from MacPorts?
>
> General-purpose answers to either question are not possible. Each affec
> For a test I was planning to adapt the migration approach. Save the
> ‘requested’ list. Uninstall all ports. Temporary mv /usr/bin/python out of
> the way. Build the requested list.
>
> I can do this on a secondary system.
>
> This would tell me at least that the ports I have installed all in
SIP is only the beginning of your boot disk headaches.
Starting with Catalina, and continuing into Big Sur, Apple made it
increasingly difficult to make any modifications to anything in the system
volume. In Catalina, the root volume was split into two: the System volume
and Data volume, and the S
=> $cd
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports
=> fgrep -R '/usr/bin/python' * \
| awk -F ':' '{print $1}' \
| sort -u \
| wc -l
67
bjarne@MacPro 19:06:33
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tar
$=> cd
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports
$=> fgrep -R '/usr/bin/env python' * \
| awk -F ':' '{print $1}' \
| sort -u \
| wc -l
140
bjarne@MacPro 19:16:42
/opt/local/var/macports/sources/rsync.macports.org/macports/releas
"#!/usr/bin/env python" might not be a problem
iff
the macports python is also installed as a prerequisite
the ${PATH} variable includes '/opt/local/bin'
Ryan Schmidt wrote:
> On Feb 19, 2022, at 11:06, Gerben Wierda wrote:
>
>> But how does one (a) find out the dependency exists
On Feb 24, 2022, at 12:35, Bjarne D Mathiesen wrote:
> "#!/usr/bin/env python" might not be a problem
> iff
> the macports python is also installed as a prerequisite
> the ${PATH} variable includes '/opt/local/bin'
The /opt/local/bin/python symlink will only exist if the user has used
15 matches
Mail list logo