Re: [Slashcode-general] OSX Installation Revisited - Slash on Tiger

[Craig H. <cra...@go...>]

Thanks Shane, I'll give it another go tonight. I have a couple of questions
though:

If I'm installing a seperate instance of Apache from the default one, can I
use the binary or will I have to install it with make install, and will it
include mod_perl?

Is there anything that I definately need to get via fink that's not
mentioned in the Slash install file?

Cheers,
Craig

On 25/09/2007, shane <sh...@lo...> wrote:
>
>
>  On Sep 25, 2007, at 9:39 AM, Craig Hand wrote:
>
>  I've found a couple of stories on slashcode.com regarding Slash on OSX,
> however nothing recent and I was wondering if the situation has changed any
> with Tiger (and indeed perhaps Leopard). For example, while somepody
> mentioned a good guide to installing mod_perl for OSX, AFAIK it was written
> around four years ago, and a lot has changed since then. Unlike back in the
> day, the likes of PHP4 and mod_perl can now be enabled in OSX simply by
> uncommenting them in httpd.conf, and MySQL (as well as PHP5) can be
> installed with a friendly binary.
>
> As someone who's looking to install Slash on Tiger, do any of these
> developments make things any more straightforward or does Slash still
> require everything to be built from scratch? If it's the latter, does anyone
> have any pointers for someone who's not afraid of the command line but a bit
> of a greenhorn when it comes to the likes of apt-get and make? Also, how
> does the OSX install process differ from the Linux one?
>
> Thanks!
>
>
> I do virtually all of my mod_perl/slashcode development on OSX machines.
> Typically, I don't replace the existing perl, I keep it. I install MySQL
> v5.x via one of the MySQL Installer Packages from mysql.com. I'll use fink
> or one of the other source code repo's to install some of the "extras" (ie
> GD, libreq, whatever) that don't come with the perl bundle Bundle::Slash
> (or, that perl packages w/in that bundle require).
>
>
> I do keep the stock Apache installed - but not to run slash. I install
> Apache 1.3.x from tarball and keep it in /usr/local/slash. It's not that
> you probably couldn't try and use the stock Apache, but I typically use that
> for other code development. It's easier for me if they are completely
> separate. And that way I can match the version of the tarball w/ what we are
> running in production at any given time from any given system, and I don't
> have to worry about messing with the stock Apache wrt Apple Updates (if
> any).
>
>
> As long as you follow the INSTALL documentation (I recommend setting up
> CPAN as it says, because it makes the install of Bundle::Slash _far_ easier)
> you're good to go.
>
>
> Once you have all the required software that slash needs installed,
> installation is no different from a linux box. Just 'make install'.
>
>
> If you do use the stock Apache, I would love to hear back from you as to
> how it goes and what you had to do to make it work, if anything.
>
>
>  Shane
>
>
>
>
>  --
> My slashcode stuff: http://slash.lottadot.com/
> Slashcode faq: http://slash.lottadot.com/slash-faq
> How to ask a question:
> http://www.catb.org/~esr/faqs/smart-questions.html#before
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>
>