APACHE 2.0 STATUS: -*-text-*-
-Last modified at [$Date: 2002/01/31 23:32:53 $]
+Last modified at [$Date: 2002/02/01 05:50:50 $]
Release:
For instance, try listening to port 80 and starting as non-root;
server fails with make_sock and 'no listening sockets' errors
but exits with 0 status. Even with -DONE_PROCESS -DNO_DETACH.
+ Justin says: "Is this really a showstopper? Most people won't
+ be using -DNO_DETACH and will look at the error
+ logs anyway."
* mod_rewrite's locks (win32) were broken by recent changes to the
apr_lock_t api (which we were deprecating in the first place, so
o perchild doesn't even build
o worker is also failing some of the 'cgi' subtests
(see <URL:http://Source-Zone.Org/Apache/regression/>):
+ Justin says: "Worker should be fine and passes httpd-test here.
+ perchild may need a maintainer. Are we willing
+ to release without perchild? It could be officially
+ added in a point release."
* If any request gets to the core handler, without a flag that this
r->filename was tested by dir/file_walk, we need to 500 at the very
the modules/http/config.m4 file has been renamed to
modules/http/config2.m4 to work around this problem, it should moved
back when this is fixed. rbb
+ Justin says: "Is this really a showstopper? This has been here
+ forever. What's wrong? Does this have to do with
+ autoconf or m4?"
* The Add...Filter and Set...Filter directives do not allow the
administrator to order filters, beyond the order of filename (mime)
before or after the Add...Filter(s) which are ordered by sequence of
filename extensions. At minimum, some sort of +-[0-10] syntax seems
like the quickest fix for a 2.0 gold release.
+ Justin says: "Could we delay this for a point release or 2.1?"
* Convert all instances of the old apr_lock_t type to the new
types (once they are fully supported in APR).
variable, but ab, htpasswd, etc. don't know how to pick up apr,
apr-util, etc.
Message-ID: <20020116000226.GA15991@ebuilt.com>
+ Justin says: "You could always build all of the binaries
+ statically if you don't want to let libtool
+ handle it. At most, I don't consider this a
+ a release showstopper as it is a packaging issue."
RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP: