Squirrelmail and Apache2 - a workaround

[maalth]

For those who are installing squirrelmail and have apache 2 installed, you should read this.

When emerging squirrelmail, squirrelmail is looking for apache 1 config files despite the fact the apache 2 is installed. The apache2 USE flag has no effect at all. How do you get around this problem? It's very easy. You have to change a couple of lines in the ebuild file. The necessary changes will work for any available build of squirrelmail in the /usr/portage/net-mail/squirrelmail directory . I will use 1.4.0-r1 as an example.

Open the file /usr/portage/net-mail/squirrelmail/squirrelmail-1.4.0-r1.ebuild
Change the following lines:
FROM:

HTTPD_ROOT="`grep '^DocumentRoot' /etc/apache/conf/apache.conf | cut -d\ -f2`"
HTTPD_USER="`grep '^User' /etc/apache/conf/commonapache.conf | cut -d\ -f2`"
HTTPD_GROUP="`grep '^Group' /etc/apache/conf/commonapache.conf | cut -d\ -f2`"

TO:

HTTPD_ROOT="`grep '^DocumentRoot' /etc/apache2/conf/apache2.conf | cut -d\ -f2`"
HTTPD_USER="`grep '^User' /etc/apache2/conf/commonapache2.conf | cut -d\ -f2`"
HTTPD_GROUP="`grep '^Group' /etc/apache2/conf/commonapache2.conf | cut -d\ -f2`"

Keep in mind that you may have to do this if there is an updated version of squirrelmail. I hope this helps someone.

[cchapman]

Why dont you submit a new ebuild that checks to see if Apache or Apache2 is installed.

[maalth]

I may do that. Thanks for the suggestion.

--Update 28 June 2003
The ebuild has been completely changed so that it's not looking for any version of apache.

[cchapman]

you da man.

[puke]

Yeah nice one, it works!