A recent commit by idl0r has reintroduced bug #300730 for mod_perl-2.0.5. Please fix this regression again. === Start of original bug report === I'm using apache[-threads], perl[ithreads] and mod_perl. Since rev 1.13 of the mod_perl-2.0.4-r1 ebuild, that setup won't work any more, since the only possible combinations are apache[threads] with perl[ithreads] or apache[-threads] with perl[-ithreads]. I assume this strict dependency is an error. It should be perfectly all right for perl to be compiled with threading support (and thus some degree of thread safety) and still use it in a single-threaded web server environment. So please change the deps back to: DEPEND="... || ( www-servers/apache[-threads] dev-lang/perl[ithreads] )" The meaning is that we depend on both apache and perl, and we either want apache to be unthreaded or perl to be thread-safe. === End of original bug report === I see no reason for a threads USE flag unless it actually changes something in the way that mod_perl itself is built. If there is a reason, though, then the dependencies should imo be something like this: threads? ( dev-lang/perl[ithreads] ) !threads? ( www-server/apache[-threads] )
Fixed in CVS.
