> On 17 Apr 2022, at 16:13, Ryan Schmidt <ryandes...@macports.org> wrote:
>> Doing the (normally unnecessary) migrations run at least will catch the >> dependencies during build. > > Only for ports you actually build, not for ports for which you receive a > binary archive. Agreed. But then, the install from my view still succeeds, even if I get a 12.2 build installed on a 12.3 system. What then is left is that potential runtime dependency. Still, doing it with force compile would be better. I am going to do that as well. >> Numbers do not give a definitive answer to major or minor updates. E.g. >> tomcat 8.2 or 8.3 are minor updates, but tomcat 8.5 was/is in fact a major >> update at the company I work, because it was fundamentally changes. The >> numbers are just a clue, not reality. See also Lifecycle Management – Let >> the Sunshine in > > In the case of macOS version numbers as they relate to a need to follow the > migration instructions, they do. The migration instructions are for helping > you upgrade from one major macOS version to another. They are not needed for > minor OS version updates. Agreed. I was misusing the migration instructions (an unnecessary ‘migration') in an attempt to do an as-clean-as-possible build with the largest chance to run into any hidden dependency on the availability of /usr/bin/python. Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>) R&A IT Strategy <https://ea.rna.nl/> (main site) Book: Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/> Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>
