The problem is in the 'reconfig' script that the rt ebuild provides. It uses two environment variables ( PN and PVR ) that aren't actually set when the webapp-config script is ran manually. Since they're not set, a very crucial bit of final processing/configuration gets skipped - which is the cause of the problem: the /var/www/<vhost>/rt-<version>/*/*.pm's end up with config variables that point to /usr/share/webapps/rt/<version>/hostroot/rt-<version>/*/*.pm's This results in a serious misconfiguration where the webapps root is used rather than the vhost document root. # PN=rt; PVR=3.4.5; export PN PVR # webapp-config -I -h <vhost> -d rt rt <version> ... will force things to work correctly. When the 'vhosts' USE flag is _not_ set, and the webapp-config gets ran automatically, then those env vars are available at the time the script runs, and everything works out with no issues. So I don't know whether this is simply a documentation bug ( http://wiki.bestpractical.com/index.cgi?GentooInstallGuide ), or whether it is an ebuild bug. I'm guessing that the best fix would be to have the /usr/share/webapps/rt/<version>/hooks/reconfig script end up containing the correct PN and PVR values in whatever manner is the right way of doing that sort of thing in portage. Something to the affect of: --- reconfig 2006-01-26 14:10:33.000000000 -0700 +++ reconfig-fix 2006-02-17 22:56:08.000000000 -0700 @@ -1,4 +1,6 @@ #!/bin/bash +PN=${PN:-rt} +PVR=${PVR:-3.4.5} PF=${PN}-${PVR} die() {
please upgrade to webapp-config-1.50.10
Verified that upgrading to webapp-config-1.50.10 solved the reported issue.
