Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Mar 2009 15:36:26 +1100 (EST)
From:      Ian Smith <>
To:        Ruben de Groot <>
Cc:        Christoph Kukulies <>,
Subject:   Re: mod_php5 and apache22
Message-ID:  <>
In-Reply-To: <>
References:  <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Tue, 24 Mar 2009 16:46:16 +0100 Ruben de Groot <> wrote:
 > On Tue, Mar 24, 2009 at 03:20:26PM +0100, Mel Flynn typed:
 > > On Tuesday 24 March 2009 15:13:33 Christoph Kukulies wrote:
 > > > I moved a site from some FreeBSD 5.2 or something (with apache2 and
 > > > mod_php5 at that time,
 > > > about 3 years old) to 7.1 (Beta though) and apache22.
 > > >
 > > > Now I don't find something that looks like mod_php5 in /usr/ports/www.
 > > >
 > > > Has that changed somehow?
 > > 
 > > lang/php5 with APACHE_MODULE ticked in options dialog.
 > The apache module compile is off by default since somewhere in 2006 and I keep
 > forgetting that occasionally :(
 > So people using pkg_add -r php5 will not get mod_php5.

That's right, you haven't been able able to install mod_php5 from a 
package for at least that long.  I've never understood the rationale.

 > This is probably not what they expected.

I could well be wrong, but I've always suspected that _most_ people who 
install apache (1.3 or 2.x) and php do so because they intend to use it 
with mod_php, rather than the command-line php interpreter or the cgi.

 > Would it not be a good idea to (re)introduce www/mod_php5?

Yes.  As far as I can tell, all that would be required is an identical 
port (with a new name, '+mod_php' would do fine) with the ONLY change 
being to select the APACHE_MODULE option on, as Mel points out.

I wish someone who knows about ports building would just do that.
Then you could again install apache+mod_php from packages, right from 
the dist CDs/DVD if desired.  Ah, for the good old days when it wasn't 
assumed that everyone had both fast boxes and fast net connections :)

cheers, Ian

Want to link to this message? Use this URL: <>