https://github.com/actions/virtual-environments/issues/5583
> GitHub Actions is starting the deprecation process for macOS 10.15.
While the image is being deprecated, You may experience longer queue
times during peak usage hours. Deprecation will begin on 5/31/2022 and
the image will be fully
On 2022-6-16 03:14 , René J.V. Bertin wrote:
On Wednesday June 15 2022 17:10:01 Christopher Jones wrote:
what about configure.universal_archs though, have you set that to have > 1 entry ?
thats what base cares about, hence the "due to < 2 supported universal_archs
A! That works, indeed.
On Wednesday June 15 2022 17:10:01 Christopher Jones wrote:
>what about configure.universal_archs though, have you set that to have > 1
>entry ? thats what base cares about, hence the "due to < 2 supported
>universal_archs
A! That works, indeed. It seems that this variable is empty when
> On 15 Jun 2022, at 3:25 pm, René J.V. Bertin wrote:
>
>
>> Base is exactly smart enough. When supported_archs contains only 1 arch, it
>> does make sense to offer a universal variant, therefore base prevents it.
>
> As I said before, supported_archs contains x86_64 and arm64.
what about
Yeah, hit me up with this, I have the 13 beta and maintain iTerm2. iTerm2
is getting harder and harder to maintain as a port - I'm starting to wonder
if it might be worthwhile to just download the correct binary, or just
abandon it as a port. I don't like the idea of abandoning it as a port -
but
>Base is exactly smart enough. When supported_archs contains only 1 arch, it
>does make sense to offer a universal variant, therefore base prevents it.
As I said before, supported_archs contains x86_64 and arm64.
If ports should be able to create a universal variant in case that variant
On Jun 14, 2022, at 12:33, René J.V. Bertin wrote:
> On Monday June 13 2022 04:34:46 Ryan Schmidt wrote:
>
>> The standard universal variant has no content. (Universal support is
>> implemented by adding the return value of procedures like
>> [get_canonical_archflags cc] to CFLAGS.) Many ports
