Change History (6)
comment:1 by , 16 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | Apache httpd 2.2.10 → Apache httpd 2.2.11 |
comment:2 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 16 years ago
Just another question about that section commenting out the isapi-module. I assume we are primarily acting on Linux systems so I'd propose to remove that section at all since isapi is only supported on Win32 ("Compatibility: Win32 only", see http://httpd.apache.org/docs/2.2/mod/mod_isapi.html) - even it compiles, installs and loads fine on Linux. Further more, the section is refering to gcc-4.1.2 while LFS has gcc-4.3.2 in the meanwhile. Not sure whether this compiler failure still exists.
comment:4 by , 16 years ago
As far as the name goes it can go either way, and since it has always been just Apache, we may as well keep it like that. Note the text on the Apache web site:
"The Apache HTTP Server Project is proud to announce the release of version 2.2.11 of the Apache HTTP Server ("Apache"). This version is principally a bugfix release."
Note that they even reference it stand-alone as "Apache". Additionally, they refer to it as the "Apache HTTP Server", not Apache-httpd.
Concerning the isapi-module, perhaps it would be best to simply put some text in the book that says don't use it as it is for Windows only.
And last, typically we use an entity to refer to a BLFS version of software so that (in this case for example) when GCC is updated, the text in the book will automatically be updated as well.
Always try to avoid hard-coding any type of version string as this becomes a maintainence trap.
comment:5 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
In addition to the version upgrade I'd like to rename the package from "Apache" to "Apache-httpd". Just like it is done at "Apache-Ant". Any thoughts?