On Mar 28, 2021, at 18:04, Fred Wright wrote:
> On Fri, 26 Mar 2021, Ryan Schmidt wrote:
>> On Mar 24, 2021, at 17:50, Joshua Root wrote:
>>
>>> we would have to set up a self-hosted runner.
>>
>> People have expressed interest in this (for x86_64) every now and then over
>> the years, but
On 2021-3-29 10:04 , Fred Wright wrote:
Does MacPorts play nicely with chroot?
Unfortunately macOS doesn't play nice with chroot. I looked into it
years ago for MPAB and I expect it's only gotten worse since.
- Josh
On Fri, 26 Mar 2021, Ryan Schmidt wrote:
On Mar 24, 2021, at 17:50, Joshua Root wrote:
we would have to set up a self-hosted runner.
People have expressed interest in this (for x86_64) every now and then
over the years, but as of now we have no ability to do this. Software
would need to
On Mar 24, 2021, at 17:50, Joshua Root wrote:
> we would have to set up a self-hosted runner.
People have expressed interest in this (for x86_64) every now and then over the
years, but as of now we have no ability to do this. Software would need to be
written to allow this to happen. And then
On 2021-3-25 09:17 , Herby G wrote:
Any chance we can have macOS 11 ARM64 CI enabled for pull requests in
the macports-ports repo?
I'm aware it would create confusion as there are probably a lot of ports
today that will fail outright on ARM64, so PRs that would pass the CI on
all the x86_64
Any chance we can have macOS 11 ARM64 CI enabled for pull requests in the
macports-ports repo?
I'm aware it would create confusion as there are probably a lot of ports
today that will fail outright on ARM64, so PRs that would pass the CI on
all the x86_64 builders would get marked as failed due
