I have a number of custom modifications to RT. These include a few custom Perl libraries and a few custom Mason hooks and extension. Generally, one installs RT so that there two install locations: main and site. I see that the ebuild has provided something for this for the Perl libraries, but uses the same Mason component path for both the main and site components. I expect my components to exist in a separate component root as is the norm for RT. I expect that this can be fixed by adjusting the www-apps/rt-3.2.1.ebuild by changing the line that reads: s|/usr/local/html|${MY_HTDOCSDIR}| to: s|/usr/local/html|${MY_HTDOCSLOCALDIR}| or whatever is appropriate. Reproducible: Always Steps to Reproduce: As a work around, I just have cfengine hacking the /usr/lib/RT.pm to alter the component directory variable to an acceptable separate location.
Andrew, Thanks for the filing the bug. I'm not as familiar with Mason, so I overlooked the necessity of having them separate. Please try rt-3.4.2, and see if that resolves the issue. $MasonLocalComponentRoot now is ${P}/local/html.
