| 1 |
> You still haven't posted posted a *single example* of webapp-config |
| 2 |
> brokeness. You, I'd say you should either back up claims about "all the ways |
| 3 |
> in which webapp-config is broken" or apologize to the concerned developers |
| 4 |
> for false claims. |
| 5 |
> |
| 6 |
> Still waiting. |
| 7 |
> |
| 8 |
|
| 9 |
OK, here is one. It seems that webapp-config silently assumes your |
| 10 |
webserver is apache by default. If a user uses lighttpd for example, |
| 11 |
this is totally incorrect. |
| 12 |
|
| 13 |
Now, this doesn't cause webapp-config to fail to emerge, but the first |
| 14 |
time you emerge any webapp, you get a big nasty error about no Apache |
| 15 |
group available, which further requires the end user to dig around the |
| 16 |
webapp-config manpage to figure out the correct file to edit *just* to |
| 17 |
get a silly php script to install in the correct location. |
| 18 |
|
| 19 |
And please, don't tell me this is a feature. It breaks noninteractivity |
| 20 |
for every "webapp" in the entire tree. |
| 21 |
|
| 22 |
-Steve |
| 23 |
-- |
| 24 |
gentoo-dev@g.o mailing list |
Archives