On Sep 16, 2009, at 9:16 PM, Ryan Schmidt wrote:
There are some issues in 1.8.0, yes. "port load" isn't working which
might affect you if you want to run server processes; in that case,
use the longer "sudo launchctl ..." commands. There is an issue if
the top-level directory you're installing into is a symlink, so
don't do that. There are several issues if your MacPorts install is
not owned by root, so use a normal root-owned install for now. We
now pass "-arch" all the time, not just for universal builds, and
this breaks some ports -- in particular glib2 is broken due to this
on PowerPC. I will look into this soon. Any other issues you're
thinking of?
You can always build MacPorts from source in a totally different
prefix, keeping your current MacPorts installation untouched, to
test if everything builds ok.
I am not doing anything out of the ordinary. php, mysql, apache2, and
pureftpd. Do you know of any issues with those?
As time moves on, Dovecot and Postfix will probably make there way to
the machine, but I am not sure at this time. Thanks
--
Scott * If you contact me off list replace talklists@ with scott@ *
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
