On Fri, November 25, 2005 6:08 am, Igor Pechtchanski wrote:
On Thu, 24 Nov 2005, Max Bowsher wrote:
I'm preparing a new Apache 2 release, and want to include a conf.d
arrangement to allow additional module packagess to install
configuration fragments in a useful way.
So far, my tentative
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor Pechtchanski wrote:
On Thu, 24 Nov 2005, Max Bowsher wrote:
I'm preparing a new Apache 2 release, and want to include a conf.d
arrangement to allow additional module packagess to install
configuration fragments in a useful way.
So far, my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Morrison wrote:
On Fri, November 25, 2005 6:08 am, Igor Pechtchanski wrote:
On Thu, 24 Nov 2005, Max Bowsher wrote:
I'm preparing a new Apache 2 release, and want to include a conf.d
arrangement to allow additional module packagess to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm preparing a new Apache 2 release, and want to include a conf.d
arrangement to allow additional module packagess to install
configuration fragments in a useful way.
So far, my tentative proposal is:
Include /etc/apache2/conf.d/*.conf in
On Thu, 24 Nov 2005, Max Bowsher wrote:
I'm preparing a new Apache 2 release, and want to include a conf.d
arrangement to allow additional module packagess to install
configuration fragments in a useful way.
So far, my tentative proposal is:
Include /etc/apache2/conf.d/*.conf in
