>> From: firstname.lastname@example.org [mailto:email@example.com]
>> Sent: Thursday, August 31, 2006 10:56 AM
>> To: ruby-talk ML
>> Subject: [ANN] open4-0.6.0
>> open child process with handles on pid, stdin, stdout, and
>> stderr: manage
>> child processes and their io handles easily.
> I tried to download the .tgz file from the RubyForge page,
but I get a
> 404. I noticed you have the files layed out somewhat
> 1 file per release it looks like. Maybe that's confusing RubyForge.
hmm. the same script uploaded the gem, which is fine, as the
tgz so i'm not sure what's going on... it looks like it may
be a rubyforge issue - i can't even delete the release with
it throwing errors (missing parameters??)
for now you can grab the tarball/gem here
sorry for hassle...
> May I suggest putting related files under the same release? Take a
> look at http://rubyforge.org/frs/?group_id=735 for what I mean.
isn't that how i have it
Not exactly. For example, I see this under alib:
Instead of just:
I didn't even realize that GForge allowed identical release names for
the same package. Maybe this has nothing to do with the problem,
however. I'm just guessing.
> Anyway, assuming this works on Windows (it does, right?)
then I might
> have to start a petition to include it in the stdlib.
errr - no. ;-(
however. i would __love__ to make it so. can i ask you to
have a look at the source and see what it would take to make
work? i'm sure this will mean factoring out fork or
requiring one of you windows libs that do so - and that may be all.
It would require C I'm afraid. The win32-open3 package is one of those
that can't properly be converted to pure Ruby. Perhaps a simple facade
is in order.
next i'll have you help me make posixlock cross-platform
I haven't looked at the source yet, but I suppose I would start with
Lock() and LockEx():
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.
On Fri, 1 Sep 2006, Berger, Daniel wrote:
>> -----Original Message-----