On Tue, Apr 20, 2004 at 12:31:25AM -0400, Joey Hess wrote: > I'm sending this mail because of an installation report which included these > comments: Thanks Joey, didn't yet have time to process this. > > - apache2 was default, but apache2+php4 module = not working It is, as of today, the php4 module for apache2 is in Sarge. PHP-team: congratualations. > > - installing both php4 and php4-cgi, makes apache2 use the cgi version of php4. Not inlogical, because php4 is for apache 1.3 only. I filed a bug to make the package names more clear: #244573: Please rename php4 to libapache-mod-php4, and make php4 dummy depending libapache{, 2}-mod-php4 But, because it is very doubtful this will be done before Sarge is released, I filed a bug against the package descriptions, which should be easy solvable, and still be quite effective IMHO: #244571: php4: Package description suboptimal, might cause confusion to new sarge installers > > - apt-get --purge remove apache2 gave warnings about files in /etc (I > > didn't touch the config), apache2 remained running after apache2 was > > gone. Installing apache (1.3) didn't make it start running) There are purge failures already reported in #197986, #237030 and #239571. Due to the oldness the oldest bug, I think patches are appreciated, I'll see what I can do about it, but can't promise anything. Don't know about the keep-running, seems not reported, and I didn't report it... Apache maintainers, what do you think? > > - The php4 readme.debian had outdated info (and very unorganized) about how to > > enable the php4 module in apache (you need to run modules-update apache > > enable mod_php4), which should be done by postinst imho anyway (didn't > > happen, don't know whether it's intentional). I reported already: #244564: php4's README.Debian outdated w.r.t. apache1.3 In the php4 (<- binary package) README it's already noted that the auto-register as module is broken, this is AFAICS not reported though, and don't know whether this is planned to be fixed. > > - Installing php4-cgi installed in apache2 automatically... don't know whether > > that's how it's supposed to work (php4 should be preferred if both are > > available imho) There is actually a whishlist open against libapache2-mod-php4 to perform exactly this current behaviour, #228343: Automatic installation in apache2, but it apparantly isn't closed. If you install libapache2-mod-php4, it is enabled by default too, if you install php4-cgi afterwards, the module is still used. Don't know what happens though if you first install php4-cgi, and afterwards libapache2-mod-php4. Should be tried IMHO. > Is there a problem with php4 and apache2, and does any of the rest of this > look like something apache2 should get a bug report for? Basically most of this is unclearness about that if you want php4 support in apache2, you should NOT install the php4 package, but the libapache2-mod-php4 package, and that the php4 package's description doesn't say anything about this doesn't help. This render IMHO Bug#244571 to something that really should be tried very hard to be fixed before Sarge, ideally even #244573 too, but the latter has more risks. Thank you all for your attention, and for creating those packages. To make Sarge the greates Debian release ever, a little bit work on the documentation and usability side still has to be done though. --Jeroen -- Jeroen van Wolffelaar Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl
Attachment:
pgpMSS2BPehl2.pgp
Description: PGP signature