Framing the MacPorts discussion

[Bjarne D Mathiesen]

Ryan Schmidt wrote:
> I personally am not comfortable adding other build machines to our buildbot system that I do not control. When I control the machines, I know what is installed on them and that they are set up correctly. Having build machines located outside of my local network also poses additional challenges, as I've learned by having our Apple Silicon build machine outside of my network, challenges which I would prefer to minimize, not increase.
> 
> We currently use one build machine per OS version / arch, and have the hardware needed to do that. Adding more hardware such that we have more than one build machine per OS version / arch is not something our buildbot system was ever designed to accommodate, and would introduce problems.

So we are more-or-less single-point-of-failure regarding the buildbots
!? Personally, I'ld deem it advisable to have at least 3 complete
systems geographically dispersed.

> 
> Using Linux and commodity hardware is not applicable because it the macOS EULA only permits running macOS on Apple hardware, as we currently do.

So it's not the proposed software stack that's the problem, but the
hardware stack. Then how about an old 2010/12 MacPro with all the bells
and whistles ? I've been able to boot a 2010 MacPro w/ 256GB RAM under
Ubuntu without any problems.

-- 
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
-----------------------------------------------------------------------
denne besked er skrevet i et totalt M$-frit miljø
OpenCore + macOS 10.15.7 Catalina
MacPro 2010 ; 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC
ATI Radeon RX 590 8 GB