Summary: | Can qmailadmin/vqadmin be made to work w/ webapp.eclass? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stuart Herbert (RETIRED) <stuart> |
Component: | Current packages | Assignee: | Qmail Team (OBSOLETE) <qmail-bugs+disabled> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | ufs |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | [webapp-apache.eclass] | ||
Package list: | Runtime testing required: | --- |
Description
Stuart Herbert (RETIRED)
![]() I guess this bug should also cover vqadmin too? Best regards, Stu nope, they need a lot of information at compile-time. vqadmin in itself deals with all of the virtual mail domains properly anyway. they would have to be statically installed in a web instance somewhere. it doesn't even like being moved around after you have installed it. couldn't we export to our environment a variable for example like: export VHOST="our.vhost.com" and the ebuild would check if this var was set, and use it instead of the default to localhost? Closing this as CANTFIX, then... |