When i got up to the point of emerging apache, going trough the gentoo desktop guide, doing the "emerge apache php mod_php mod_ssl" command, gentoo emerged both apache 1.3 and apache 2.0 . I'm gonna remove one of them, but still i think it is a bug emerging apache and getting both versions. Reproducible: Always Steps to Reproduce: 1.Clean install 2.emerge apache php mod_php mod_ssl 3. Actual Results: Both apache 1.3 and 2.0 are merged Expected Results: install just one version of apache (possibly the stable one 1.3)
I've narrowed it down a bit. It seems that mod_ssl dependes on apache 1.3, while the stable version installed i the 2.0 Proposed fix: change the mod_ssl ebuild, so it depends on apache 2.0 instead of 1.3 Alfredo Matos
apache2 has mod_ssl integrated into it ... the fact you got 1.x and 2.x is Bug 4698
Ok, my bad. Apache 2 doesnt require mod_ssl to be installed. The ebuild is correct, working with --enable-ssl So this is a documentation bug. Because the now stable apache is 2.0.x . And the guide still works with 1.3 , where mod_ssl is still required to be installed aside from apache 1.3 . Fix: Change the documentation to express: apache 2.0.x no longer requires mod_ssl to be merged , it's standard with the apache 2 package. This way the user doesnt end up with both apache installed, if following the guide and wanting ssl support Alfredo Matos
Created attachment 15816 [details, diff] Patch to desktop guide Changed everything so it resembles apache2, remove all instances of mod_ssl. However, this is based on a system that had apache2 before it went stable, I hope someone with a better view on this can review the patch.
This is all valid, we should ammend that asap on the desktop-guide. Steph
committed
