This might result in larger lists of dependencies, but it is the best way to keep compatibility. It even still works on 10.4 Tiger as a legacy platform, but no additional effort will be put into this to support new features.įor this, it is vitally important not to rely on the system version, but to install dependencies into the MacPorts prefix. Usually there is support for the latest two releases of Mac OS X, at the moment this is 10.5 Leopard and 10.6 Snow Leopard.
Is MacPorts really " Breaks like Gentoo but you can't fix it like Gentoo", or does it say "32 bit? Legacy! EMacPorts developers do their best to test on various systems and support multiple configurations.
Macports broken ports how to#
MacPorts in this regard seems only like Gentoo in that you can get breakage by trying to keep your system up-to-date as intended.Įarlier breakage had me stumped about how to install Django now I have Django installed, but its breaking on upgrading glib1 the last substantive change on the bug ( ) was about a year ago. But after further experience it seems not to be exactly like Gentoo: with Gentoo, things break regularly, but you can often find a solution by Googling salient portions of an error message, and unlike computer situations in general it makes quite rational sense to try again 24 or 48 hours later if something is broken. Among Linuxes, keeping up-to-date with MacPorts struck me as being most like Gentoo (arguably the least Mac-like entry on the shortlist of major Linux distributions).
0 kommentar(er)
