4 ms·
I almost went the other way (from ports to brew) because of the complex manual procedure required to fix ports when you upgrade the OS: https://trac.macports.o
by kbutler 10y ago
I almost went the other way (from ports to brew) because of the complex manual procedure required to fix ports when you upgrade the OS:
https://trac.macports.org/wiki/Migration https://trac.macports.org/wiki/Migration
After going through the migration, it isn't that bad, but it was surprising (horrifying?) to me that ports was completely broken after an OS upgrade.
- deleted 10y ago[deleted]
- raimue 10y agoMacPorts dev here. Problems can arise when some ports have local patches for specific versions of macOS. This might work at first, but could lead to build failures or other problems later. Some ports also hardcode the OS version into their binaries. The simple way to prevent this kind of stuff is to rebuild all ports for the new platform. Probably there would be room for improvement, but there is only little interest by contributors. This only happens once a year and after everybody went through it, they quickly loose interest in contributing anything better for the migration process.