Bug 300730

Summary:	www-apache/mod_perl-2.0.4-r1: don't force apache[threads]
Product:	Gentoo Linux	Reporter:	Martin von Gagern <Martin.vGagern>
Component:	[OLD] Server	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	http://sources.gentoo.org/viewcvs.py/gentoo-x86/www-apache/mod_perl/mod_perl-2.0.4-r1.ebuild?r1=1.12&r2=1.13
Whiteboard:
Package list:		Runtime testing required:	---

Description Martin von Gagern 2010-01-12 14:25:51 UTC

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 to something like this:
DEPEND="...
www-servers/apache
dev-lang/perl
|| ( 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.

As far as I understand things, that's what the has_apache_threads_in function from depend.apache.eclass used to enforce as well, so it should work if it did work so far.

Comment 1 Benedikt Böhm (RETIRED) gentoo-dev

2010-01-12 14:52:06 UTC

thanks, much better solution :)

Comment 2 Martin von Gagern 2011-07-03 19:37:10 UTC

This bug has been reintroduced for 2.0.5; regression tracked in bug #373943.