[gentoo-dev] Re: [gentoo-user] How to get rid of Apache2

["Dhruba Bandopadhyay" <dhruba@codewordt.co.uk>]

CC: gentoo-dev for raising documentation and consistency issues
Subject: Apache2 with mod_php

<quote who="Robin H.Johnson">
> On Mon, May 26, 2003 at 05:56:33PM +0100, Dhruba Bandopadhyay wrote:
>> I emerged apache and being on ~x86 it got apache2.  Now since there
>> was no way in hell it was ever going to work with php for me I removed
>> it.
> Something is wrong here. I maintain PHP, and my primary testing is done
> on Apache2. I've been using Apache2 and PHP together on production
> servers since before I started using Gentoo quite successfully.
>
> Could you please file a bug about what doesn't work for you.

Hello

I have been driven to utter frustration by this issue as everyone claims
to have apache2 and mod_php working but no one tells me how.  :(

robbat2, I initially emailed on gentoo-dev
(http://marc.theaimsgroup.com/?l=gentoo-dev&m=105362815721103&w=2) posing
this very question and got this reply
(http://marc.theaimsgroup.com/?l=gentoo-dev&m=105362905522592&w=2) which I
obeyed but to no avail.  I have also looked unsuccessfully many times on
#gentoo for apache and php devs.

Here's the scenario.  If after reading you still feel I should file a bug
then I'll do so.  There are two issues at hand here.  Firstly, there's an
inconsistency with versioning.  Imagine a freshly installed gentoo desktop
(not server) system without apache installed.  The system has ~x86 set but
not apache2 since the user does not wish to use apache2.  He (or she) then
proceeds to 'emerge apache mod_php'.  Now bearing in mind that the apache2
use flag is *not* set this now emerges apache2 but then proceeds to
compile mod_php *without* apache2 support.  Doesn't this seem like a
complete contradiction?

(-) I suggest policy be rethought on this matter and that consistency be
achieved so that mod_php is compiled with support for the version of
apache that it is intended to accompany.

(-) Should apache2 really be installed as default on ~x86 given the number
of problems that myself and other users on forums have suffered,
especially, when the apache2 flag is unset?  I realise that use flags do
not determine package installation but only optional support but this is
to provide some food for thought.

The second issue here is about what went wrong.  On machine 1, my desktop,
apache1 was already installed and when I moved to ~x86, apache2 was
automatically emerged during updates.  So I recompiled mod_php with
support for apache2.  I ran the ebuild /var/db/... config commands and
restarted apache2 but got some errors.  I tried a few modifications but
once again got some other errors.  I don't have the errors to hand anymore
but can try to reproduce sometime if you wish.  On machine 2, apache had
never been installed and so I added apache2 to use flags and emerged
apache2 and mod_php.  Then following instructions I ran:

$ ebuild /var/db/pkg/dev-php/mod_php-4.3.1-r3/mod_php-4.3.1-r3.ebuild config

and got:
/usr/sbin/ebuild.sh: line 88: //usr/sbin/apacheaddmod: No such file or
directory

Incidentally, I have just tried to emerge mod_php again and got:
----
$ emerge mod_php
Calculating dependencies ...done!
>>> emerge (1 of 1) dev-php/mod_php-4.3.1-r3 to /
>>> md5 src_uri ;-) php-4.3.1.tar.bz2
>>> Unpacking source...
 * This ebuild is intended for ~x86 testing presently. Heavy testing welcome.
 * It should be stable for nearly systems.
>>> Unpacking php-4.3.1.tar.bz2 to /var/tmp/portage/mod_php-4.3.1-r3/work
 * Applying fix for PEAR world writable files                            
[ ok ]
 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 *
 *   /usr/portage/distfiles/php-4.3.1-db4.diff.gz
!!! ERROR: dev-php/mod_php-4.3.1-r3 failed.
!!! Function epatch, Line 181, Exitcode 0
!!! Cannot find $EPATCH_SOURCE!
----

I would really appreciate some official documentation on how to get
apache2 working with mod_php and mod_ssl and also the subtle differences
between apache1&2.  Following the current desktop configuration guide and
ebuild postinst works for apache1 but not for 2.  I'd also be curious to
hear your thoughts about the versioning issues.

With regards
Dhruba Bandopadhyay



--
gentoo-dev@gentoo.org mailing list