openbsd-ports/net/p5-POE-Component-Resolver/distinfo

MD5 (POE-Component-Resolver-0.912.tar.gz) = zu36LSkmj7v7gcBa7Ov7qg==
RMD160 (POE-Component-Resolver-0.912.tar.gz) = tQ9NJQ9IEnnGsoO/3DGHzVSY5Ms=
SHA1 (POE-Component-Resolver-0.912.tar.gz) = wlUFlgTId2HU10YneyFsaAyjOi4=
SHA256 (POE-Component-Resolver-0.912.tar.gz) = dWSNzUQbtgy1e+2Wq4rhbSaQGvbZUSx7f2W4XtUePeQ=
SIZE (POE-Component-Resolver-0.912.tar.gz) = 26709
import p5-POE-Component-Resolver-0.912 POE::Component::Resolver performs Socket::GetAddrInfo::getaddrinfo() calls in subprocesses where they're permitted to block as long as necessary. By default it will run eight subprocesses and prefer address families in whatever order Socket::GetAddrInfo returns them. These defaults can be overridden with constructor parameters. from wen heping (MAINTAINER), needed by upcoming p5-POE update, not hooking this up yet. ok sthen@ 2011-05-11 14:59:59 -04:00			`MD5 (POE-Component-Resolver-0.912.tar.gz) = zu36LSkmj7v7gcBa7Ov7qg==`
			`RMD160 (POE-Component-Resolver-0.912.tar.gz) = tQ9NJQ9IEnnGsoO/3DGHzVSY5Ms=`
			`SHA1 (POE-Component-Resolver-0.912.tar.gz) = wlUFlgTId2HU10YneyFsaAyjOi4=`
			`SHA256 (POE-Component-Resolver-0.912.tar.gz) = dWSNzUQbtgy1e+2Wq4rhbSaQGvbZUSx7f2W4XtUePeQ=`
			`SIZE (POE-Component-Resolver-0.912.tar.gz) = 26709`