fielding 98/10/06 13:46:34
Modified: . STATUS
Log:
Remove things done today and increase priority of binary build discussion.
Revision Changes Path
1.503 +44 -55 apache-1.3/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/apache-1.3/STATUS,v
retrieving revision 1.502
retrieving revision 1.503
diff -u -r1.502 -r1.503
--- STATUS 1998/10/05 23:04:28 1.502
+++ STATUS 1998/10/06 20:46:32 1.503
@@ -18,6 +18,48 @@
* need to ensure it compiles properly on win32 before rolling the
tarball, and that no last minute changes break it
+ * How should an Apache binary release tarball look?
+
+ 1. The "old" way where it is just a source release tarball
+ plus a pre-compiled src/httpd-<gnutriple>. It is created
+ via the apache-devsite/binbuild.sh script which
+ - creates the build tree
+ - creates the src/Configuration file with standard modules
+ - runs "make"
+ - renames src/httpd to src/httpd-<gnutriple>
+ - runs "make clean"
+ - packs the build tree stuff together
+ Already known discussion points:
+ - should src/httpd be renamed or now because a lot
+ of PRs say they cannot find the httpd :-(
+ Status: Ralf -0, Ken +0
+
+ 2. The way other projects release binary tarballs, i.e.
+ a package containing the installed (binary) files.
+ It can be created by a script which
+ - creates the build tree
+ - runs "./configure --prefix=/usr/local/apache \
+ --enable-shared=remain \
+ --disable-module=auth_db \
+ --enable-suexec ..."
+ - runs "make install root=apache-root"
+ - packs the stuff together from ./apache-root only!!
+ Already known discussion points:
+ - should there be a prefix usr/local/apache in
+ the tarball or not? Some people think
+ it's useful while others dislike it a lot.
+ - it doesn't include the source.
+ - should suexec be prebuilt in a binary tarball?
+ Status: Ralf +1, Martin +1, Ken -1 (not a veto), Roy -1
+
+ 3. A source release tarball with three extra directories:
+ lib: for the shared library object files
+ bin: for the httpd and support executables
+ man: for the man files (if desired)
+ as if the server was installed in those directories.
+ Status: Roy +1
+
+
Documentation that needs writing:
* Need a document explaining mod_rewrite/"UseCanonicalName off" based
@@ -47,24 +89,11 @@
Message-ID: <[EMAIL PROTECTED]>
Status: Ralf +1, Lars +1
- * Paul's patch to add integrated restart/shutdown signalling (Win32)
- This patch make Apache listen on predictable event names to allow
- restarts and shutdowns to be initiated. Also adds a new command line
- option to send the shutdown or restart signal to the running parent
- process.
- Message-ID: <[EMAIL PROTECTED]>
- Status: Ken +1 (on concept), Lars +1 (on concept), Jim +1 (concept)
- Martin +1 (on concept; the restart switches could
- be added to the unix version, too)
-
In progress:
* Ken's IndexFormat enhancement to mod_autoindex to allow
CustomLog-like tailoring of directory listing formats
- * Roy is working on the 100 Continue problem with calls to
- ap_discard_request_body()
-
Needs patch:
* Ralf: mod_so doesn't correctly initialise modules. For instance
@@ -147,45 +176,6 @@
You can differentiate by comparing the output of `uname -m' with any
of: alpha bebox macppc newsmips ofppc pica pmax sparc64.
- * How should an Apache binary release tarball look?
- NOTE: This should be resolved before 1.3.3 !!
-
- 1. The "old" way where it is just a source release tarball
- plus a pre-compiled src/httpd-<gnutriple>. It is created
- via the apache-devsite/binbuild.sh script which
- - creates the build tree
- - creates the src/Configuration file with standard modules
- - runs "make"
- - renames src/httpd to src/httpd-<gnutriple>
- - runs "make clean"
- - packs the build tree stuff together
- Already known discussion points:
- - should src/httpd be renamed or now because a lot
- of PRs say they cannot find the httpd :-(
- Pros: <gets filled tomorrow>
- Cons: <gets filled tomorrow>
- Status: Ralf -0, Ken +0
-
- 2. The way other projects release binary tarballs, i.e.
- a package containing the installed (binary) files.
- It can be created by a script which
- - creates the build tree
- - runs "./configure --prefix=/usr/local/apache \
- --enable-shared=remain \
- --disable-module=auth_db \
- --enable-suexec ..."
- - runs "make install root=apache-root"
- - packs the stuff together from ./apache-root only!!
- Already known discussion points:
- - should there be a prefix usr/local/apache in
- the tarball or not? Some people think
- it's useful while others dislike it a lot.
- - it doesn't include the source.
- - should suexec be prebuilt in a binary tarball?
- Pros: <gets filled tomorrow>
- Cons: <gets filled tomorrow>
- Status: Ralf +1, Martin +1, Ken -1 (not a veto)
-
* Redefine APACHE_RELEASE. Add another 'bit' to signify whether
it's a beta or final release. Maybe 'MMNNFFRBB' which means:
MM: Major release #
@@ -277,9 +267,8 @@
gzipped variants of files when both variants exist on the server.
* Roy's HTTP/1.1 Wishlist items:
- 1) Expect
- 2) byte range error handling
- 3) update the Accept-Encoding parser to allow q-values
+ 1) byte range error handling
+ 2) update the Accept-Encoding parser to allow q-values
* use of spawnvp in uncompress_child in mod_mime_magic - doesn't
use the new child_info structure, is this still safe? Needs to be
