Re: RFC on packaging of additional Apache2 modules

2005-11-25 Thread John Morrison
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 proposal is:

 Include /etc/apache2/conf.d/*.conf in httpd.conf.
 Have module packages install config fragments to
 /etc/apache2/conf-std.d/, and copy them insto conf.d if no equivalent
 exists.

 This is consistent with the way the package currently handles
 httpd.conf, etc.

 I'm posting here for input before I go ahead and do it.

 The above sounds fine, but why not use /etc/defaults/etc/apache2/conf.d/
 instead of /etc/apache2/conf-std.d/?
   Igor

That's amost the same as Debian is doing (the only linux I'm running atm)...

/etc/apache2/apache2.conf
/ some standard apache config stuff then lines to include...
# Include module configuration:
Include /etc/apache2/mods-enabled/*.load
Include /etc/apache2/mods-enabled/*.conf

# Include all the user configurations:
Include /etc/apache2/httpd.conf

# Include ports listing
Include /etc/apache2/ports.conf

# Include generic snippets of statements
Include /etc/apache2/conf.d/[^.#]*

/etc/apache2/conf.d/
/ site specific config files (I think)
/etc/apache2/envvars
/ any standard vars (I've not got any)
/etc/apache2/httpd.conf
/ this file is basically empty too
/etc/apache2/magic
/ usual magic instructions
/etc/apache2/mods-available/
/ contains *all* known module information
/etc/apache2/mods-enabled/
/ contains links to the modules in mods-available you want to use
/etc/apache2/ports.conf
/ just a listen 80 instruction here!
/etc/apache2/README
/ Huh, think you can guess ;)
/etc/apache2/sites-available/
/ contains all sites you might want this installation of apache to host
/etc/apache2/sites-enabled/
/ links to the sites to you want to enable from sites-available
/etc/apache2/ssl
/ ssl files

Hope this helps.

J.

PS, I agree with Igor, untar the installation files into
/etc/defaults/etc/apache2/... and postinstall copy as appropriate :)



Re: RFC on packaging of additional Apache2 modules

2005-11-25 Thread Max Bowsher
-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 tentative proposal is:

Include /etc/apache2/conf.d/*.conf in httpd.conf.
Have module packages install config fragments to
/etc/apache2/conf-std.d/, and copy them insto conf.d if no equivalent
exists.

This is consistent with the way the package currently handles
httpd.conf, etc.

I'm posting here for input before I go ahead and do it.
 
 
 The above sounds fine, but why not use /etc/defaults/etc/apache2/conf.d/
 instead of /etc/apache2/conf-std.d/?

I chose /etc/apache2/conf-std.d/ to be similar to
/etc/apache2/httpd-std.conf and /etc/apache/ssl-std.conf, the naming of
which originates from the upstream Apache package.

Max.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)

iD8DBQFDhtD6fFNSmcDyxYARAmc7AJ9Pg29+npvRcpfcRsXO/Ijt/19zWQCgktrn
8yjoG39jZ1ZsTj12b7CE4F8=
=SCgX
-END PGP SIGNATURE-


Re: RFC on packaging of additional Apache2 modules

2005-11-25 Thread Max Bowsher
-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 install
configuration fragments in a useful way.

So far, my tentative proposal is:

Include /etc/apache2/conf.d/*.conf in httpd.conf.
Have module packages install config fragments to
/etc/apache2/conf-std.d/, and copy them insto conf.d if no equivalent
exists.

This is consistent with the way the package currently handles
httpd.conf, etc.

I'm posting here for input before I go ahead and do it.

The above sounds fine, but why not use /etc/defaults/etc/apache2/conf.d/
instead of /etc/apache2/conf-std.d/?
  Igor
 
 
 That's amost the same as Debian is doing (the only linux I'm running atm)...

There's a reason for that - Debian is the only linux _I'm_ running atm. :-)

[snip Debian layout]

The Debian layout is nice, though I hesitate to depart so far from the
upstream package as they do, especially when 2.2 is approaching,
bringing with it a redesigned standard config layout.

Max.


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)

iD8DBQFDhtJUfFNSmcDyxYARAjc8AJ0ZbyT+hK92ct78JXoUUx3+j5an3ACeOilF
62xdGT2AQ92X5Uuc69HthSM=
=IHdD
-END PGP SIGNATURE-


RFC on packaging of additional Apache2 modules

2005-11-24 Thread Max Bowsher
-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 httpd.conf.
Have module packages install config fragments to
/etc/apache2/conf-std.d/, and copy them insto conf.d if no equivalent
exists.

This is consistent with the way the package currently handles
httpd.conf, etc.

I'm posting here for input before I go ahead and do it.


Max.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)

iD8DBQFDhhGnfFNSmcDyxYARAk0PAKCETNklBlZLSaGguNg1Vc1QbdGTBgCeODwR
m3ohHeK3YA7PcAzIH3p7yv8=
=FHbM
-END PGP SIGNATURE-


Re: RFC on packaging of additional Apache2 modules

2005-11-24 Thread Igor Pechtchanski
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 httpd.conf.
 Have module packages install config fragments to
 /etc/apache2/conf-std.d/, and copy them insto conf.d if no equivalent
 exists.

 This is consistent with the way the package currently handles
 httpd.conf, etc.

 I'm posting here for input before I go ahead and do it.

The above sounds fine, but why not use /etc/defaults/etc/apache2/conf.d/
instead of /etc/apache2/conf-std.d/?
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA