In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote: > If you look carefully, you'll see I said I would have to "stick with > debian" when developing my LAMP apps. This means I am trying to > replicate my debian environment (Apache 2 with MP2, TT2, other gunk) > on my Mac. This requires more work than it should perhaps. Not least > because fink is not apt-get and some things are in fink, some are in > Macports and some are in neither. I rely on debian sid and apt-get to > have the latest software from CPAN, and when it doesn't, I try and > package it for debian which is why I am part of the debian-perl team. > I am happy to compile from source, but I loose all the work on > security and compatibility from upstream when I do - not a good trade > off. > > When I work on my Mac, I expect everything to "just work." Perhaps > this is wrong when it comes to a development environment for the > reasons stated in this thread and elsewhere on this list but I > thought impatience was virtue for a programmer. In any case, I never > refused to develop for the Mac. <Insert snarky emoticon here.>
Hm. I run Slash (the code that runs Slashdot) on my Mac. Everything does Just Work for me. Perl, Apache, mod_perl, TT, MySQL. Although I build from the source on both Mac *and* Linux (except MySQL, which I get binaries from in both cases), so maybe that's the difference. Not sure what you mean by losing things from upstream. -- Chris Nandor [EMAIL PROTECTED] http://pudge.net/ Open Source Technology Group [EMAIL PROTECTED] http://ostg.com/