Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes

2021-06-25 Thread Tabitha McNerney
Maybe the pkg installer software looks to see if an installation is trying to mkdir in root and it automatically creates /etc/synthetic.conf with an entry. That would be quintessential Apple to do something like that. Thank you Apple, it just works. On Fri, Jun 25, 2021 at 5:20 PM Ryan Schmidt w

Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes

2021-06-25 Thread Ryan Schmidt
On Jun 25, 2021, at 21:03, Tabitha McNerney wrote: > On a fresh Catalina or Big Sure system, if you cd to root / then sudo then > try mkdir /opt or something else such as mkdir /hello the system won't allow > it, I get this: > > mkdir: /hello: Read-only file system > > note: the MacBook I just

Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes

2021-06-25 Thread Tabitha McNerney
On a fresh Catalina or Big Sure system, if you cd to root / then sudo then try mkdir /opt or something else such as mkdir /hello the system won't allow it, I get this: mkdir: /hello: Read-only file system note: the MacBook I just tried this on also has FileVault enabled and its got one of those A

Re: MacPorts and /opt/local on Catalina and Big Sur read only volumes

2021-06-25 Thread Ryan Schmidt
On Jun 25, 2021, at 18:07, Tabitha McNerney wrote: > Hi all, > > I haven't installed a fresh MacPorts system in quite some time but will soon > be doing so on a few Macs one running Catalina and the other Big Sur. > Starting with Catalina, the root volume / is read-only so how do the MacPort

Re: Clean install of Big Sur and MacPorts but old Xcode

2021-06-25 Thread ChrisF
On 26/06/21 3:39 pm, Ryan Schmidt wrote: On Jun 25, 2021, at 16:39, ChrisF wrote: I've upgraded to Big Sur (11.4) using a clean install followed by a restore of all users( except MacPorts) from a Time Machine backup. I also restored apps. When I went do a clean install of MacPorts I saw that

MacPorts and /opt/local on Catalina and Big Sur read only volumes

2021-06-25 Thread Tabitha McNerney
Hi all, I haven't installed a fresh MacPorts system in quite some time but will soon be doing so on a few Macs one running Catalina and the other Big Sur. Starting with Catalina, the root volume / is read-only so how do the MacPorts package installers set things up such that /opt/local can remain

Re: Why don't p5-* ports mark their dependencies?

2021-06-25 Thread Ryan Schmidt
On Jun 12, 2021, at 13:07, Bill Cole wrote: > On 2021-06-12 at 12:55:24 UTC-0400 (Sat, 12 Jun 2021 09:55:24 -0700) > Ken Cunningham is rumored to have said: > >> macports recommended perl is still 5.28 > > Which has been unsupported upstream for just over a year. The point Ken was making is tha

Re: Why don't p5-* ports mark their dependencies?

2021-06-25 Thread Ryan Schmidt
On Jun 12, 2021, at 12:39, Kastus Shchuka wrote: >> sudo port upgrade --enforce-variants git -perl5_28 +perl5_30 > > Thank you, that worked and allowed me to uninstall all p5.28 modules. > > What puzzles me still, why port info shows that git depends on perl 5.28 > modules: > > $ port info git

Re: Warning: invalid universal_archs configured (should contain at least 2 archs)

2021-06-25 Thread Ryan Schmidt
On Jun 16, 2021, at 03:17, André-John Mas wrote: > I have recently started getting the following warning: > > "Warning: invalid universal_archs configured (should contain at least 2 > archs)" > > I have looked through the FAQ, a web search and what might seem to be > relevant documentation,

Re: Clean install of Big Sur and MacPorts but old Xcode

2021-06-25 Thread Ryan Schmidt
On Jun 25, 2021, at 16:39, ChrisF wrote: > I've upgraded to Big Sur (11.4) using a clean install followed by a restore > of all users( except MacPorts) from a Time Machine backup. I also restored > apps. > > When I went do a clean install of MacPorts I saw that XCode was still present > in

Clean install of Big Sur and MacPorts but old Xcode

2021-06-25 Thread ChrisF
I've upgraded to Big Sur (11.4) using a clean install followed by a restore of all users( except MacPorts) from a Time Machine backup. I also restored apps. When I went do a clean install of MacPorts I saw that XCode was still present in Applications, had a bit of a brain fade and assumed that