When doing a tinderbox run with squirrelmail 1.4.5, I received the following error: /usr/portage/eclass/webapp.eclass: line 350: /etc/vhosts/webapp-config: No such file or directory !!! ERROR: mail-client/squirrelmail-1.4.5 failed. !!! Function webapp_pkg_setup, Line 350, Exitcode 1 !!! Unable to open file /etc/vhosts/webapp-config !!! If you need support, post the topmost build error, NOT this status message. /usr/portage/eclass/webapp.eclass: line 452: /etc/vhosts/webapp-config: No such file or directory * * This ebuild did not call webapp_src_install() at the end * of the src_install() function * * Please log a bug on http://bugs.gentoo.org * * You should use emerge -C to remove this package, as the * installation is incomplete * !!! ERROR: mail-client/squirrelmail-1.4.5 failed. !!! Function webapp_pkg_postinst, Line 466, Exitcode 0 !!! Ebuild did not call webapp_src_install() - report to http://bugs.gentoo.org !!! If you need support, post the topmost build error, NOT this status message.
(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.
