upgrading to Sequoia, all worked flawlessly but port migration very very slow

[Chris Jones]

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