Currently, webapp-config always appends its idea of the application name to the directory when installing. This is one misfeature with two adverse effects: 1. If I want horde to be accessible at "www.example.com/tinkerbell", I should be able to do that. I shouldn't *have* to use "/horde" or "/tinkerbell/horde". 2. This is the one that's my main beef: I need to be able to specify that a webapp is at the document root. I *actually* want my horde to be accessible at horde.example.com. My docroot should be /var/www/horde.example.com/htdocs, into which I should be able to install horde (and not /var/www/horde.example.com/htdocs/horde). This is prevented by webapp-config's insistence on appending "horde." (Yes, at the moment, I easily work around this by setting my docroot to /var/www/horde.example.com/htdocs/horde, but that is not a general solution.) Some switch needs to be made available to either modify the effective app name (suffix?) or prevent it from being appended altogether. Of course, some webapps have hardcoded web paths. Perhaps there should be something in the metadata that specifies whether an app supports relocation (it should still let you do it, though, with a warning).
If you don't have the vhosts USE flag set, it's policy for emerge (through the webapp eclass) to tell webapp-config to install the package into -h localhost -d <packagename>. Just add USE=vhosts, and then you can run webapp-config manually to install as many copies of the package into whatever directories you want. Best regards, Stu
vhosts is already in my USE flags. I'm referring to manual webapp-config installations (emerge didn't do one automatically since "vhosts" was already there).
This isn't a webapp-config bug. It's a problem with horde. If you look in /usr/share/webapps/horde/*/htdocs, I bet you'll find a 'horde' directory under there. That's your problem. Best regards, Stu
Aha! I get it now. So when spanky fixes Bug #55070, this will be fixed at the same time. Thanks...sorry for missing which package caused the problem.
Marking as duplicate of 55070.
*** This bug has been marked as a duplicate of 55070 ***