Re: Re: status of dio

From: Date: Mon, 09 Oct 2006 17:59:30 +0000
Subject: Re: Re: status of dio
References: 1  Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-4236@lists.php.net to get a copy of this message
# Sergio.Paternoster@h3g.it / 2006-10-09 17:26:59 +0200: > From: Pierre [mailto:pierre.php@gmail.com] > On Mon, 9 Oct 2006 17:19:50 +0000 neuhauser@sigpipe.cz (Roman Neuhauser) wrote: > > > > what's up with dio? I'd like to use it, is it going to be released > > > anytime soon? > > > > Given that the maintainers has not commited anything since 4 years, you > > should not have too much hope. The only changes were done when the > > extension was still in PHP. > Yes, I checked the package several times. Anyway, what we have at the > moment is working good... dio is a would-be dependency of a unit testing library I've been writing[1]. If I'm going to have my program packaged for BSDs[2] and Linux distributions[3], the packaging and installation processes need to be hassle-free[4]. So, if dio *does* work, can someone with enough karma release it? It's a shame the code rots in the repository instead of being used. [1] http://codex.sigpipe.cz/testilence/ [2] BSD ports/pkgsrc rely on fetching tarballs and building from source much more than the various RPM-based systems; cf Gentoo. [3] RedHat etc. probably wouldn't feel the urge to build a rpm of dio from a checkout because my wimpy package wants it... So they wouldn't distribute my package. [4] It's not impossible to write a port that runs cvs co instead of fetching a tarball (*if the cvs server does not require login*), but it's impossible for quite a few people to access tcp/2401. -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991

« previous php.pecl.dev (#4236) next »