-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have test Apache 2.2 packages happily serving on my machine right now. There are a few issues regarding the transition which I want to air ahead of time for possible comments:
1. Configuration file compatibility Apache 2.0 configuration files won't work unmodified for 2.2. The *almost* will, but several modules have changed name, so the LoadModule lines need to be updated. In addition to the basic 'will it work?' question, the Apache 2.2 default configuration has been _greatly_ reworked for clarity, removing many lesser-used settings to supplementary files which can be Included if needed. Options: (A) In postinstall, programmatically edit the LoadModule lines. (B) In postinstall, move the user's config aside, and install the new default. (C) Do nothing automatically, put a large note in the announcement email, and in the Cygwin README file. I'm inclined to opt for (C), because (A) would allow users to avoid thinking about the major rewrite of the default configuration, and I don't want to encourage people to simply progress to 2.2 without realizing that this is a non-trivial upgrade. (B), whilst appearing attractive to me at first, seems not so good on reflection: Better that the server not start, than it revert to default configuration. 2. Subversion compatibility The main reason I've been holding off releasing Subversion 1.3.0, is that the subversion-apache2 package can be compatible with Apache 2.0 OR 2.2, but not both. I'm intending to switch to 2.2 with 1.3.0, rather than doing the switch at some 1.3.x patch release, which is generally expected to be a painless upgrade. Max. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) iD8DBQFEAuIifFNSmcDyxYARAseUAKCD150uumpvv5SQv0Y5jh6Gn5LEBgCgm1GQ mZOn1zK5ibwKm9nlpzc2l+g= =KvoC -----END PGP SIGNATURE-----
