5 ms·
One of the problems with all these systems is that they don't identify which software components are already installed on OS X by Apple natively, and to use tho
by kngspook 18y ago
One of the problems with all these systems is that they don't identify which software components are already installed on OS X by Apple natively, and to use those for dependencies when possible. So you wind up with two Perls, two Pythons, two Rubys, etc., each with slightly different versions...
- davidmathers 18y agoThat's a feature, not a bug. Your original system stays clean and if you mess up your fink or macports installation you can just throw the whole thing in the trash and start over from scratch.
- kngspook 18y agoWhat's wrong with only installing Python/Perl/Ruby if the native one doesn't satisfy the dependencies, as opposed to (currently) installing it every time?
- puppetsock 18y agoThe problem is that the versions of the non-macports Ruby/Python/etc aren't managed by the ports system. So you're in for weird dependency mismatches if you upgrade your system version of Python. Self-contained keeps it simpler. Just use a script to set up your $PATH as needed.
- davidmathers 18y agoThe people who tried to get the Gentoo Portage system running on OS X a few years ago tried that idea. It ended in tears.
- gtani 18y agoone of the Oreilly tiger manuals gives stern warnings not to move or rename or delete the perl and python that tiger installed. I think that still goes for Leopard, as well as for the factory ruby