I built 2.4.3 with the options
./configure \
--prefix=$tdir \
--with-apr=$adir \
--with-apr-util=$adir \
--without-ssl \
--without-crypto \
--disable-cache \
--without-distcache \
--enable-maintainer-mo
Hi Roy,
On 18.08.2012 22:07, Roy T. Fielding wrote:
I built 2.4.3 with the options
./configure \
--prefix=$tdir \
--with-apr=$adir \
--with-apr-util=$adir \
--without-ssl \
--without-crypto \
--disable-cache \
It's '--enable-maintainer-mode' which introduces this behavior. When
being built for mere mortals, we are much nicer as far as which
modules are built and loaded by default
Maybe --enable-maintainer-mode should be renamed --enable-developer-mode
On Aug 18, 2012, at 4:07 PM, Roy T. Fielding
On Aug 18, 2012, at 1:45 PM, Rainer Jung wrote:
> Yes, before 2.4.0 we introduced exactly this difference. All modules that
> were build get a LoadModule line in the installed config, but most are
> commented out. I don't have the list of modles active by default at hand
> though.
Ah, okay.
>
On 19.08.2012 00:20, Roy T. Fielding wrote:
On Aug 18, 2012, at 1:45 PM, Rainer Jung wrote:
Yes, before 2.4.0 we introduced exactly this difference. All modules that were
build get a LoadModule line in the installed config, but most are commented
out. I don't have the list of modles active by
On Sunday 19 August 2012, Roy T. Fielding wrote:
> > Partial answer: the current semantics of maintainer-mode is (per
> > configure help):
> >
> > "Turn on debugging and compile time warnings and load all
> > compiled modules"
>
> Umm, WTF? Why?
One reason was to make it easier for httpd develo
