invisible universal variant and merger_must_run_binaries
ken.cunningham.webuse at gmail.com
Tue Feb 2 17:18:51 UTC 2021
Just wanted to point out a potential issue with the universal variant
Let's assume a user on a BigSur Intel system wants to build some
software +universal to support arm64.
One port needed +universal has some tricks in it, and requires
"merger_must_run_binaries". That port cannot be built universal on an
Intel system (which can't run arm64) but can be built universal on an
arm64 system (which can run Intel). So let's say that universal port is
built, and uploaded to the buildbot or similar.
Joe Schmoe on BigSur Intel could download and install that port
+universal, and be on his way.
But now, his system will never see that port could be universal (because
he can't built it universal), and the chain collapses, some would say
So -- how to elegantly handle this issue, if possible?
More information about the macports-dev