Re: apache2: clearing the air [please read]

[Erik Steffl <steffl@bigfoot.com>]

Wichert Akkerman wrote:
> 
> Previously Daniel Stone wrote:
> > It's packaged differently. Very differently. Web pages no longer go
> > (directly) to /var/www, CGI scripts no longer go to /usr/lib/cgi-bin (at
> > all), logs don't go to /var/log/apache2.
> 
> I don't care why you did this, it is a violation of Debian policy
> and it means all existing packages that install CGIs or webpages
> will not work with apache2.
> 
> Why not change things to have /var/www and /usr/lib/cgi-bin as locations
> for the default virtual host and allow the admin to specify the location
> for other hosts? That fits the FHS (and LSB) which explicitly leave
> that up to the admin.

  what you are saying is basically let's not bother with it, let
administrator screw up the system.

  in the end, it does not matter whether it's administrator who creates
virtual hosts or debian - if they are against debian policy (or do not
conform to standard file system layout) it's bad (think about it, we
don't have policy for policy's sake, we have it for a reason).

  there has to be a way to create virtual hosts - if debian policy
currently does not allow it (does not mention virtual hosts (and as
other pointed out it's not only about web servers)) the policy has got
to change (I don't say that what apache2 team did is the best solution).

  it's often said that in computing you only have three numbers: 0, 1,
n. So the question is - do we provide one apache instance or n? There is
nothing special about one of these so why have a default treated as a
special case?

	erik