Public SourceMage Discussion List

["Sergey A. Lipnevich" <sergey AT optimaltec.com>]

I commented on the bug on changes I know of. I don't think we should get 
into the business of repairing someone's configuration if it doesn't 
work with a new version, especially with such a complex thing as 
httpd.conf, so here's what I'd like to suggest.
Firstly, I think apache22 is not necessary, as module writers seem to be 
catching up 2.2. Secondly, we can change the apache2 spell to mark all 
files in /etc/httpd as "configuration" (that's where most of the visible 
changes are), which is not straight-forward but probably doable. This 
will give us backup by sorcery. Finally, we upgrade the spell and keep 
it in test a little longer.
What do you think?

BTW, if you want to test the new version, cast httpd-dev.

Sergey.

David Kowis wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> http://bugs.sourcemage.org/show_bug.cgi?id=10405
>
> I wanted to bring this bug to the attention of the mailing list, as it
> will affect almost everyone that uses Source Mage and has apache
> running. The latest release of apache will likely require a rewrite of
> the spell, as the configuration has been redone. Also, some modules have
> changed names, so the existing on-disk config (/etc/httpd/*) will be
> different. So I wanted to bring to the attention of everyone here:
> Do we update the apache2 spell to this newer version, or have another
> apache22 spell? The differences aren't as great as the 1.x to 2 changes,
> but still different.
>
>