You still haven't posted posted a *single example* of webapp-config
brokeness. You, I'd say you should either back up claims about "all the ways
in which webapp-config is broken" or apologize to the concerned developers
for false claims.
Still waiting.
OK, here is one. It seems that webapp-config silently assumes your
webserver is apache by default. If a user uses lighttpd for example,
this is totally incorrect.
Now, this doesn't cause webapp-config to fail to emerge, but the first
time you emerge any webapp, you get a big nasty error about no Apache
group available, which further requires the end user to dig around the
webapp-config manpage to figure out the correct file to edit *just* to
get a silly php script to install in the correct location.
And please, don't tell me this is a feature. It breaks noninteractivity
for every "webapp" in the entire tree.
-Steve
--
[email protected] mailing list
