I have emerge viewcvs-0.9.2-r3 and this ebuild configure and install this file /etc/apache2/conf/modules.d/47_viewcvs.conf Because in future version this file is remove. It is found in doc directory? It it possible to integrate on emerge ? Sorry for my bad english Thanks Reproducible: Always Steps to Reproduce: 1. 2. 3.
Antonio, I am not sure what your question is. If you are concerned that the apache config file found in /etc/apache2/conf/modules.d will be removed when you unmerge or upgrade viewcvs---Portage protects config files in /etc, so the config will not be unmerged. Please clarify if that's not your concern. Best, Renat
OK, my question is: If i emerge viewcvs-0.9.2-r3 the file 47_viewcvs.conf is collocate in /etc/apache2/conf/modules.d/ but if i emerge any other version this file is collocate in /usr/share/doc/viewcvs-...... and manually put in modules.d. pkg_postinst() { ewarn "Before using viewcvs make sure you configure it correctly" einfo "There is a sample apache integration configuration file in the" einfo "documentation directory named: apache.conf" } pkg_postinst() { ewarn "Before using viewcvs make sure you configure it correctly." einfo "There is a sample apache integration configuration file in the" einfo "documentation directory named: apache.conf" einfo "If you're using apache2 this configuration is already done for" einfo "you in /etc/apache2/conf/modules.d/47_viewcvs.conf" } It is possible to integrate this features in any version in portage ?
It's possible, but won't happen until webapp-config gets a better handler of different httpds. This is on Stuart's todo list, and I'd rather wait and fix it correctly than provide custom solutions for each webserver in Portage.