I think our apache-www/mod_lisp port has some problems. The ebuild for apache-www/mod_lisp-1.x is for apache2, while the ebuilds for apache-www/mod_lisp-2.x is for apache1. Therefore, due to the version numbers, If you emerge mod_lisp, you'll get apache1. I'd like to split mod_lisp into mod_lisp (apache1) and mod_lisp2 (apache2). I thought of combining them into the one ebuild, like in mod_jk, but its really not possible in mod_lisp's case, since they're distributed separarely, and they'll be problems whenever the mod_lisp module for apache2 has version numbers like 2.x which will conflict with the mod_lip module for apache1 (currently 2.x also). I don't think slotting helps either in this situation.
It looks like this is how upstream is calling the package as well. Since that's the case, I agree the package should be split. It looks like we've never had a stable mod_lisp2, so it shouldn't be too difficult.
I split these ebuilds out into mod_lisp and mod_lisp2.
(In reply to comment #2) > I split these ebuilds out into mod_lisp and mod_lisp2. > mod_lisp has versions which allow the amd64 architecture - one citing amd64 and one citing ~amd64. mod_lisp2 OTOH neither cites NOR masks amd64. How complex would it be to get at least ~amd64 for mod_lisp2?
If you can confirm it works for you on amd64, I will add ~amd64 keywords for you. Unfortunately, access to a amd64 this week is limited.
