<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font size="2">sorry for the question because I read too fast,
and saw after there's a buildbot.<br>
</font></p>
<p><font size="2">and last question : the same operation, upgrade to
macOS 15 and port selfupdate, port upgrade outdated, on another
m1 (my laptop) did not show the same message : "need for
migration"... Why was this alert not issued in this particular
case?</font></p>
<font size="2">thanks</font>
<p></p>
<div class="moz-cite-prefix">Le 29/10/2024 à 10:23, Chris Jones via
macports-users a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:a338cc94-d776-4300-a7dc-82153682249f@hep.phy.cam.ac.uk">
<br>
<br>
On 29/10/2024 1:11 am, Fabien Auréjac wrote:
<br>
<blockquote type="cite">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.
<br>
<br>
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...?
<br>
<br>
On Sonoma compiling seemed to be really faster... Is this due to
the process of migration ?
<br>
<br>
Or is it a regression of performance due to some sort of macOS
performance or security clamping ?
<br>
</blockquote>
<br>
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.
<br>
<br>
Chris
<br>
</blockquote>
</body>
</html>