I saw on the rt-users mailing list archive that the rt2 ebuild should work with apache2. I set the apache2 USE flag, and did an emerge -p to check the dependencies, but it still depends on apache 1.3 (ignoring apache2 flag) : # ACCEPT_KEYWORDS=~x86 emerge -p www-apps/rt These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] dev-perl/Scalar-List-Utils-1.14 [ebuild N ] dev-perl/IPC-ShareLite-0.09 [ebuild N ] dev-perl/Cache-Cache-1.03 [ebuild N ] dev-libs/mm-1.3.0 [ebuild NS ] net-www/apache-1.3.33 [ebuild N ] dev-perl/mod_perl-1.29 [ebuild N ] net-www/mod_ssl-2.8.21 [ebuild N ] dev-perl/Apache-Test-1.15 [ebuild N ] dev-perl/libapreq-1.3 [ebuild N ] dev-perl/Class-Container-0.11 [ebuild N ] dev-perl/HTML-Mason-1.26 [ebuild N ] dev-perl/log-dispatch-2.10 [ebuild N ] dev-perl/text-wrapper-1.000 [ebuild N ] dev-perl/locale-maketext-fuzzy-0.02 [ebuild N ] dev-perl/Text-Tabs+Wrap-2001.0929 [ebuild N ] dev-perl/text-reform-1.11 [ebuild N ] dev-perl/text-autoformat-1.12 [ebuild N ] dev-perl/Text-Quoted-1.7 [ebuild N ] dev-perl/FCGI-0.67 [ebuild N ] dev-perl/HTML-Scrubber-0.08 [ebuild N ] dev-perl/Font-AFM-1.19 [ebuild N ] dev-perl/regexp-common-2.117 [ebuild N ] dev-perl/HTML-Tree-3.18 [ebuild N ] dev-perl/Test-Manifest-1.11 [ebuild N ] dev-perl/XML-RSS-1.04 [ebuild N ] dev-perl/HTML-Format-2.04 [ebuild N ] dev-perl/Test-Builder-Tester-1.00 [ebuild N ] dev-perl/Sub-Uplevel-0.09 [ebuild N ] dev-perl/Test-Exception-0.15 [ebuild N ] dev-perl/Tree-Simple-1.12 [ebuild N ] dev-perl/text-template-1.44 [ebuild N ] dev-perl/WWW-Mechanize-1.04 [ebuild N ] dev-perl/Module-Versions-Report-1.02 [ebuild N ] dev-perl/i18n-langtags-0.30 [ebuild N ] dev-perl/locale-maketext-1.09 [ebuild N ] dev-perl/locale-maketext-lexicon-0.38 [ebuild N ] dev-perl/Apache-Session-1.60 [ebuild N ] dev-perl/Memoize-1.01 [ebuild N ] dev-perl/Test-Inline-0.16 [ebuild N ] dev-perl/class-returnvalue-0.52 [ebuild N ] dev-perl/MLDBM-2.01 [ebuild N ] net-www/mod_fastcgi-2.4.2 [ebuild N ] dev-perl/Want-0.07 [ebuild N ] dev-perl/dbix-searchbuilder-1.01 [ebuild N ] www-apps/rt-3.2.1 Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: apache2 installed.
could you do some testing for us? copy the ebuild to your overlay, and bump the revision #. Then apply the following patch to the new revision file: --- rt-3.2.1.ebuild 2004-09-07 12:16:36.000000000 -0700 +++ rt-3.2.1-r1.ebuild 2004-12-18 19:21:42.328612384 -0800 @@ -62,11 +62,12 @@ mysql? ( >=dev-db/mysql-4.0.13 >=dev-perl/DBD-mysql-2.0416 ) postgres? ( >=dev-db/postgresql-7.4.2-r1 dev-perl/DBD-Pg ) fastcgi? ( dev-perl/FCGI net-www/mod_fastcgi ) - !fastcgi? ( =dev-perl/libapreq-1* ) - =net-www/apache-1* -" -# apache2? ( >=net-www/apache-2 dev-perl/FCGI net-www/mod_fastcgi ) -# !apache2? ( =net-www/apache-1* =dev-perl/libapreq-1* ) + net-www/apache + apache2? ( >=net-www/apache-2 ) + !apache2? ( + =net-www/apache-1* + =dev-perl/libapreq-1* + )" LICENSE="GPL-2" Then please test the new ebuild under apache1 and apache2, with the fastcgi USE flag in both possible states.
Yes, of course. But hmmm. What do you mean with "bump the revision #" ?
I tried the ebuild, but... I saw no change in the "emerge -p" result: # ACCEPT_KEYWORDS=~x86 emerge -p =www-apps/rt-3.2.1 >old_rt.txt # USE="-apache1 apache2 fastcgi" ACCEPT_KEYWORDS=~x86 emerge -p =www-apps/rt-3.2.1-r1 >new_rt.txt # sort old_rt.txt >old_rt2.txt # sort new_rt.txt >new_rt2.txt # diff old_rt2.txt new_rt2.txt < [ebuild N ] www-apps/rt-3.2.1 --- > [ebuild N ] www-apps/rt-3.2.1-r1 I tried with apache1/-apache1 , apache2/-apache2 , fastcgi/-fastcgi I also changed this in the ebuild, without any change: < IUSE="mysql postgres fastcgi" < #IUSE="mysql postgres fastcgi apache2" > #IUSE="mysql postgres fastcgi" > IUSE="mysql postgres fastcgi apache2" I don't really understand how an ebuild works, so... no idea what to check now.
I found that these packages force the emerge of apache-1.x.x : mod_perl mod_ssl Those modules are dependencies of dev-perl/libapreq and libapreq of dev-perl/HTML-Mason In clear text, the problems comes from this package :-/
I just checked on HTML::Mason's home page, apache2 is supported by version 1.27 but the latest version in portage is 1.26 http://www.masonhq.com/?FAQ:Installation#h-can_i_use_mason_with_apache_mod_perl_2_0_
See http://bugs.gentoo.org/show_bug.cgi?id=81257
Folks, rt-3.4.2 is in portage. Still Apache-1 only, as mod_perl2 fails to work for me. Let's revisit this later once the Apache folks are done with their Big Move (TM).
Hi, Could you please add rt-3.2.3 ? I successfully installed rt-3.2.1 with apache2 last week, but I read that rt-3.4.x don't work with apache2 because of mod_perl2 (see http://wiki.bestpractical.com/index.cgi?ManualInstallation )
Christophe, I'd like to figure out a sensible RT + Apache2 solution - it seems to me that mod_perl2 support isn't going to stabilize any time soon. I am considering adding an apache2 USE flag, to be used with FastCGI. Once I do that, I'll try to come back and do 3.2.3.
rt-3.4.2-r1 now supports apache2 + fastcgi, as well as lighttpd. mod_perl2 support may be forthcoming, depending on the status of mod_perl2 and libapreq2 in the tree.
Hi, Thanks for your efforts :-) Since my post, my boss told me to install RT on a stand alone machine with apache1. I just finished it. How problematic is it to use apache2+fastcgi? Do you think it's safer to stay on apache1?
Please consult the documentation at http://wiki.bestpractical.com/index.cgi, and specifically http://wiki.bestpractical.com/index.cgi?PerformanceTuning
tigger^ points out to me that the reconfig hook depends on ${P} being set, which is not the case when the vhosts USE flag is set. This is a {bug || feature} of webapp-config. Stuart is planning to commit the fix tomorrow, at which point I'll update the ebuild.
hi guys. new mod_perl-2.0.1 and libapreq2-2.06 are in portage. this might help please test and see if it does. thanks.
Now that libapreq2 is unmasked, rt-3.4.2-r1 supports apache2.
