Summary: | [req] tomcat support for php | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Massimo Fantin <massimo> |
Component: | New packages | Assignee: | PHP Bugs <php-bugs> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | wltjr |
Priority: | Lowest | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Massimo Fantin
2006-04-05 07:18:08 UTC
Depending on the version of tomcat, TOMCAT_HOME or CATALINA_HOME can be in different places. I would recommend looking at /etc/conf.d/tomcat* and using the HOME value set in there. Possibly sourcing or referencing that file from ebuild to determine TOMCAT_HOME at php compile time. As this is only supported in PHP 4.X anyway, we won't support it in our PHP ebuilds, sorry, as we don't want to add another SAPI for now to maintain. But support for the MY_CONF variable was added to dev-lang/php, so you can easily pass configure parameters yourself to the ebuild: MY_CONF='--with-servlet="/opt/tomcat5"' emerge =dev-lang/php-4* Should enable you to build that SAPI, it's naturally your concern then to have the various needed variables set correctly ($CATALINA_HOME etc.), and eventually you'll have to modify the ebuild anyway to copy the correct files to the correct places (the .jar for example ???). But MY_CONF should make it a lot easier to try out *unsupported* things if you must. ;) Best regards, CHTEKK. UPDATE: the name of the varible was changed from MY_CONF to EXTRA_ECONF to follow what other ebuilds already do. Best regards, CHTEKK. |