Python, Fink, and Darwin (now MacPorts) for Mac OS

http://www.kyngchaos.com/macosx:index

http://wiki.winehq.org/MacOSX/Building

http://sourceforge.net/apps/trac/gtk-osx/wiki/Build

Steps to ensure compatibility between fink and macports

How do I know which libraries I have in UNIX? http://discussions.apple.com/thread.jspa?messageID=9761248

http://jira.freeswitch.org/browse/FSBUILD-161 Compiling On OSX

http://trac.mapnik.org/wiki/MacInstallationSource

====================================

http://www.oreillynet.com/mac/blog/2006/02/a_bad_day_for_fink_and_darwin.html

====================================

why macports python:

http://www.mail-archive.com/pythonmac-sig@python.org/msg09100.html

==================================== MacPorts - if you want to use terminal apps you have to add: #Changes to get macports working, backed original up to ~/.bash_profile_backup export PATH=$PATH:/opt/local/bin export MANPATH=$MANPATH:/opt/local/share/man export INFOPATH=$INFOPATH:/opt/local/share/info To ~/.bash_profile Also if you want screen to work with irssi (in macports) you have to install screen from macports as well, or add: shell -/bin/bash to ~/.screenrc permalink dannomac 1 point 6 months ago[-] I prefer to unset $MANPATH entirely. man finds docs automatically from $PATH, and $MANPATH is set to something stupid out of the factory. permalinkparent livedog 2 points 6 months ago[-] I just started using MacPorts a short while ago and this was one of the few thing that really annoyed me. ====================================

All that said, I don't trust either darwinports or fink do manage Python software. I will use darwinports to build the dependencies for some things, and build the Python packages myself. As far as Mac specific patches to Python software goes, I was the originator of them in many cases... so these "conveniences" don't really apply to me because I am building and hacking on these things myself anyway (and in these cases, both fink and darwinports would get in my way, which is another reason I don't use them for Python software).

I completely agree here. I've adopted a multi-prong approach which works well for me:

1. Use Apple's python (and your sweet pyobjc) for mac apps 2. Use a packaging system (fink, darwinports, whatever) for an X11 or non-gui python. This is what I use from command line. Generally I need more deps for some of this stuff, so a packaging system helps a lot here. 3. 'python setup.py install --prefix=$HOME/unix' and add $HOME/unix/lib/python2.3 to my PYTHONPATH for other stuff which isn't packaged by anyone, generally pure python stuff.

This way I keep the mucking about with my system as root to a minimum, and get reasonable value from pre-packaged stuff.

Packaging systems should be the job of the OS vendor in this day an age. To be honest, I find it shocking that Apple's packaging system doesn't have a package remove, it would make it far more viable. Even better if they adopted a real packaging system like apt wink

==================================== I compile things all the time... It is not impossible, and it does not take forever. If something does not install, it will usually say why. If you read the INSTALL or README files, they will usually list dependancies. It can be very recursive if you are trying to install something complex. I was installing ethereal, I mean wireshark, with all the bells and whistles (full gdk) and that was, fun. It took about threee hours to track down everything before it would install.

With macports, it would be "sudo port install ethereal"

I use /usr/local/ for my PREFIX for things I install, unless I want to put them in ~/bin I usually use ~/bin for things that I script

=====================================
Topic revision: 19 Jan 2010, JamesBusser
 
Download.png
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback
Powered by Olark