I’m curious if you’ve revisited the NDA recently, since a skim of the verbiage
makes it seem to me that discussing the new OSes should be OK, assuming we
don’t review it or post screenshots.
Fromhttps://developer.apple.com/support/terms/apple-developer-program-license-agreement/#ADPLA9.1:
>
I’m curious if you’ve revisited the NDA recently, since a skim of the verbiage
makes it seem to me that discussing the new OSes should be OK, assuming we
don’t review it or post screenshots. From
https://developer.apple.com/support/terms/apple-developer-program-license-agreement/#ADPLA9.1:
>
On Sep 21, 2023, at 00:26, Bryan Jones wrote:
>
> Dear MacPorts:
>
> I write to propose a policy change: a MacPorts release for a new macOS major
> version should be publicly available by the time Apple publishes the final
> Release Candidate version of macOS.
>
> Rationale: MacPorts is an
I suspect that the number of people supporting MacPorts itself (not just
specific ports) is quite small; and they're doing it in their "spare" time, at
that.
What is typically involved in updating MacPorts itself (and any ports that have
to be updated with it before others can be checked), and
Dear MacPorts:
I write to propose a policy change: a MacPorts release for a new macOS major
version should be publicly available by the time Apple publishes the final
Release Candidate version of macOS.
Rationale: MacPorts is an annual problem for me. I’m a Mac developer who needs
to install
