since several versions of php updates i discover a problem which really anoys me really. on every update of php portage changes my APACHE2_OPTS directive in /etc/conf.d/apache2. it does not only change it. it breakes the whole config. before updating php my config looks like [snip] APACHE2_OPTS="-D DEFAULT_VHOST -D INFO -D SSL -D SSL_DEFAULT_VHOST -D PERUSER -D LANGUAGE -D FASTCGI -D PHPMYADMIN_VHOST -D FOOBAR_VHOST -D FOOBAR2_VHOST ..." [/snip] after the update it looks like [snip] APACHE2_OPTS="-D DEFAULT_VHOST -D INFO -D SSL -D SSL_DEFAULT_VHOST -D PERUSER -D LANGUAGE -D FASTCGI -D PHPMYADMIN_VHOST -D FOOBAR_VHOST -D FOOBAR2_VHOST ..." -D PHPMYADMIN_VHOST -D FOOBAR_VHOST -D FOOBAR2_VHOST ..." [/snip] therefore apache wont start up apache2ctl configtest says # apache2ctl configtest /etc/conf.d/apache2: line 36: -D: command not found /etc/conf.d/apache2: line 75: unexpected EOF while looking for matching `"' /etc/conf.d/apache2: line 76: syntax error: unexpected end of file so after update i've got to fix my config file every time i update php by hand Reproducible: Always Steps to Reproduce: 1.emerge (update) php 2.try to restart apache 3. Actual Results: config file broken Expected Results: etc-update should announce about config file that should be updated imho the php ebuild should be changed to use the same api as other ebuilds does to update config files so user can update it over etc-update or dispatch-conf.
*** This bug has been marked as a duplicate of bug 300000 ***
