snortsnarf's ebuild assumes apache is installed in its default directory (/home/httpd) instead of checking the apache user's home directory. This breaks here as I have apache installed in /var/httpd (directories under /home are auto-mounted from another system).
Can you symlink /home/httpd to /var/httpd ?
In my case, no. The directories under /home are auto-mounted via NFS from another server, and I can't NFS-mount a symlink. That said, I hesitated in filing the original report, since I was never really convinced that this was a bug, so much as a special case. I'm not certain that using apache's home directory is any more valid than hard-coding /home/httpd. I modified the ebuild locally to "do what I want", but I'm not certain it's correct for everybody. In other words, if someone were to decide to simply close this bug report, I wouldn't lose any sleep over it.
Hi, Easiest way to fix this is for us to port this ebuild across to our new webapp.eclass, which we'll be releasing shortly. I've marked this bug as 'LATER'. As soon as we can, we will revisit this bug, and port the ebuild across. Thanks, Stu
Dear package maintainer, This package needs updating to be compatible with the new webapp-config tool. Please emerge net-www/webapp-config (make sure you get version 1.2 or later), and update your ebuild to work with this new tool. You can use 'man 5 webapp.eclass', 'man 5 webapp-config' and 'man 8 webapp-config' to learn more about how your ebuild needs to work. You can find an example ebuild, for phpmyadmin, in /usr/share/doc/webapp-config-1.2/ If you encounter any difficulties with the new framework (and we apologise, but there are sure to be a few at first), please let us know and we'll do our best to help you. Best regards, Stu
webapp-config compatible ebuild in portage (snortsnarf-021111.1-r2.ebuild)
