I've just updated apache to 2.2.6-r7. This version has an updated module-handling by the ebuild. This version installs a new 00_mod_autoindex.conf file at /etc/apache2/modules.d/, but does not remove the old 00_autoindex.conf. I think the best would be to rename the old file to the new one, and then etc-update them. But, if that's impossible, at least the ebuild should warn the user about the new renamed file. slightly off-topic: Similarly, the status-relative portion of 00_mod_info.conf has been moved to 00_mod_status.conf file. This new file won't be part of etc-update, while the old one will. For the user, it will look like the status module has been removed. I think the ebuild should warn the user about this change. Hey, devs, the version 2.2.6-r7 is pretty new, I think many admins will still update apache and will still have trouble with these two issues. Please, make the life easier for them by at least adding a warning/info at the end of the ebuild.
if you haent touch 00_autoindex.conf (and you should't touch it) portage would have removed it automatically
(In reply to comment #1) > if you haent touch 00_autoindex.conf (and you should't touch it) portage would > have removed it automatically I disagree. By saying "You shouldn't", you are implying that configuration files are not meant to be configured.
Well, if you modified the file then you don't want it removed since the modifications will get lost. Once we do this, we'll get the opposite bug ranting about portage removing user configuration files.
(In reply to comment #3) > then you don't want it removed since the modifications will get lost. Exactly. But in this case I don't even get a notification that this file should be renamed and merged (using etc-update or similar tool) with the new file with the new name.
(In reply to comment #2) > (In reply to comment #1) > > if you haent touch 00_autoindex.conf (and you should't touch it) portage would > > have removed it automatically > > I disagree. By saying "You shouldn't", you are implying that configuration > files are not meant to be configured. > yes, indeed, you should customize apache with your own configuration files, not those installed by the ebuild(s).
