# Re: open4-0.6.0

**URL:** <https://www.ruby-forum.com/t/re-open4-0-6-0/67128>\
**Category:** Ruby\
**Created:** [August 31, 2006, 9:49pm UTC](https://www.ruby-forum.com/t/re-open4-0-6-0/67128 "2006-08-31T21:49:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![BergerS\_Daniel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/bc8723/32.png) [@BergerS\_Daniel](https://www.ruby-forum.com/u/BergerS_Daniel)\
**Post date:** [August 31, 2006, 9:49pm UTC](https://www.ruby-forum.com/t/re-open4-0-6-0/67128/1 "2006-08-31T21:49:00Z")

</div>

> > ```
> > alib-0.4.0.gem
> > alib-0.4.0.tgz
> > 
> > ```
> > 
> > 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.
> 
> ah. didn’t know you could do that! in any case i’ve been  
> doing for a looong time so i’m sure it’s not the problem in  
> this case… i’ll look into it for my rubyforge script.

Yes, when you put out a release (using the web form) you’ll see an  
option to “Add file to this release”. That’s what I use. I prefer my  
approach because it’s a little less confusing (to me), and saves screen  
real estate. I have a feeling it’s also easier to manage in terms of  
show/edit in the Admin section.

For example, if you wanted to hide the 0.3.1 release for alib, wouldn’t  
you have to perform two edits? One for the gem and one for the .tgz  
file?

But, hey, far be it from me to tell you how to organize your project. 🙂

> > Lock() and LockEx():
> 
> interface that mimics File#flock
> 
> if you have a minute check out posixlock - it’s really short.  
> which win32 lib  
> might already have locking builtin?

The wrappers for the raw C functions would be in windows-pr  
(windows/file). However, I just realized I haven’t included the  
appropriate constants for those functions (dangit). I’ll do that this  
weekend.

I’ll take a look at posixlock and see what I can come up with.

Regards,

Dan

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.