| Summary: | Squirrelmail uses webapp-eclass incorrectly | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Chris Gianelloni (RETIRED) <wolf31o2> |
| Component: | Current packages | Assignee: | Gentoo Web Application Packages Maintainers <web-apps> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Chris Gianelloni (RETIRED)
2005-10-11 11:53:24 UTC
(In reply to comment #0) > /usr/portage/eclass/webapp.eclass: line 350: /etc/vhosts/webapp-config: No such > file or directory Uhm, if you are missing /etc/vhosts/webapp-config, then your net-www/webapp-config install is incomplete. OK, apparently you missed the point. This is a tinderbox run. This means it starts from a stage3 tarball, and performs an "emerge squirrelmail" from there. If it is showing an error, then some part of the dependency tree must be invalid somewhere with the ebuilds. This is not a live system. This is a tinderbox. This is the same thing you would get if you were to perform these actions yourself from a default stage3 tarball with no modifications. Well... it now passes the tinderbox builds. I believe that the newer webapp.eclass fixes this. Thanks to Stuart for committing a fixed eclass. |