Yesterday I emerged 'horde', a webmail webapp, but alas was unable to use it. Portage correctly installed the horde files to /usr/share/webapps/horde/2.2.5 and I then ran webapp-config to install the webapp onto a virtual host. However, even after configuring Horde it would not run. I believe this is due to the fact that webapp-config creates symlinks from the base installation to the virtual host installation and this causes problems when Horde's php scripts try to detect the resident location of the active file. The horde scripts get confused and think they are running under /usr/share/webapps/horde/2.2.5/... when they should actually determine /var/www/my.virtual.host/htdocs/horde/... to be the base directory. Not sure how to go about fixing this without modifying all of Horde's php files to determine the base directory differently, using the location of the symlinks rather than the actual file location. In the meantime, perhaps just copying the files over instead of creating symlinks will solve the issue?
*** This bug has been marked as a duplicate of 55070 ***
I'm not sure, is this really a dupe of bug 55070? That bug seems to address problems with the destination directory that horde and its submodules use, which is not the problem I'm having. I haven't even installed any submodules, just horde itself, and my problem is with symlinks and horde being unable to detect the "correct" location it is running under. Unless I'm not understanding the other bug report correctly, I believe this is a different issue.
Shawn, I have horde installed and have not observed the problem you describe. Since you're seeing symlinks, I'm assuming your using webapp-config-1.9-r2: I advise you to switch to webapp-config-1.10-r5. Due to symlink-sensitivity issues in verious webapp packages as well as apache installations, current versions of webapp-config (seems like for at least a month or more now) don't create symlinks in the virtual install directory, but rather hardlinks (be sure and read the "Hard Linking vs Soft Linking" section of the webapp-config man page after upgrading for advise on making sure that webapps are installed to a location where it's possible to hardlink them into your htdoc trees). If you need help, do something like following: # mkdir /etc/portage (unless it already exists) # echo '<sys-apps/webapp-config-1.11' >> /etc/portage/package.keywords (^^^^ putting the line in this way will allow portage to update to new revisions that Stuart may release for v1.10 even though they're not marked stable, but not to a brand new version until it *is* marked stable) # webapp-config -C -h my.virtual.host -d / # emerge -auv world (or whatever you want to do to get webapp-config updated) # etc-update ... (now, read the man page section I talked about, and if necessary, move /usr/share/webapps to a location in the partition containing your web documents and symlink it at /usr/share/webapps). # emerge horde (probably not actually necessary to remerge horde...I'm just being thorough) # webapp-config -I -h my.virtual.host -d / horde 2.2.5 Hope this helps you out.
Mike, thanks for your suggestion. I upgraded to webapp-config-1.10-r5 and that solved my problem. The only thing I had to do differently was when editing package.keywords webapp-config is in net-www rather than sys-apps. Still, this bug is NOT a duplicate of 55070. I suppose it could be marked INVALID since it's not an issue in the latest (unstable) release of webapp-config. I would change it so but I don't think I have permissions.
Okay, maybe I can mark it INVALID after all.
Baha...my brain is already in the new post-net-www-split heirarchy (http://www.gentoo.org/news/en/gwn/20040726-newsletter.xml). That is happening this week, after which webapp-config will, in fact, be in sys-apps (be sure to update your files in /etc/portage!). Sorry about that. :)
