I understand, this would be a very naive approach, thanks for the little
explanation.
Le 29/10/2024 à 11:06, Chris Jones a écrit :
On 29 Oct 2024, at 9:34 am, Fabien Auréjac <fabien.aure...@gmail.com>
wrote:
But this suggest me another question, do macports binaries upload
from my computer the results of the compilation that happened, to
help the community in later installations ?
No, that does not happen and is absolutely not something we would want
for many reasons. There are dedicated resources for these builds, see
e.g.
build.macports.org <https://build.macports.org/waterfall>
<https://build.macports.org/waterfall>
<https://build.macports.org/waterfall>
Le 29/10/2024 à 10:28, Fabien Auréjac a écrit :
Thank you, I was not aware of this. Excuse me for the mistake, I'm
quite new to language compilation concepts.
Le 29/10/2024 à 10:23, Chris Jones via macports-users a écrit :
On 29/10/2024 1:11 am, Fabien Auréjac wrote:
Hello, after upgrading to Sequoia, all worked flawlessly without
need of anything, but when I tried to update macports via port
selfupdate, it asked for a migration.
All seems to be working well, but I'm quite surprised about the
time it takes... for 500+ ports, more than 8 hours of compilation
on a macMini M1, and it's not finished...?
On Sonoma compiling seemed to be really faster... Is this due to
the process of migration ?
Or is it a regression of performance due to some sort of macOS
performance or security clamping ?
You are comparing Apples with Oranges... Currently there are no
binary tarballs for any ports on macOS15 with arm, as the buildbot
has not yet been commissioned. So consequently you have to build
everything from source which obviously takes a lot longer than a
binary install. macOS14 arm does have binary tarballs.
Chris
