I'll attach an ebuild for cl-tbnl that has better requirements. In case Apache2 is being used, nothing regarding Apache is required, if not, mod_lisp is required. This is because in an environment where Apache2 was installed, cl-tbnl tried to install mod_lips (1) and Apache (1). That's not nice. If Apache2 is preferred, we should supouse the user is going to install mod_lisp2 by hand (untill we have a package for it). Thanks. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 54917 [details] ebuild for tbnl with better mod_lisp requirements.
Created attachment 57553 [details] An update to 0.5.5 of the better mod_lisp handling.
Created attachment 64988 [details] new use flag - standalone It's a good idea, but not ideal. Cl-tbnl doesn't require apache at all. It has its own httpd server. I suggest to add one more use flag - for example standalone. So dependencies would be like this: RDEPEND="${DEPEND} !standalone? ( apache2? ( =www-apache/mod_lisp-1* ) !apache2? ( =www-apache/mod_lisp-2* ) )" Works fine for me.
I applied the suggestion from Comment #3. Still haven't completed the improved apache vs. apache2 handling, as it is dependent on getting mod_lisp for apache2 straightened out in portage.
This has since been fixed.