[Rubygems-developers] Open issues for 1.3?

Daniel Berger djberg96 at gmail.com
Sat Sep 20 09:06:00 EDT 2008

Luis Lavena wrote:


>>> I cannot suggest we use File::writable? instead since under Windows,
>>> ACLs can deny you access to a specified folder and still show up as
>>> writable, as I reported to RubySpec
>>> http://groups.google.com/group/rubyspec/browse_thread/thread/2e2b21b73aca5fcc#
>> We could add ACL based implementations for owned?, readable?,
>> writeable? and executable? in win32-file if you're interested.
> That's a chicken-egg situation: verify if the home folder is writable
> to be able to install a gem will depend on a gem to do the job :-)

Except that you ship the one-click with win32-file, right? So, we're starting 
with chicken. :)

>> Also keep in mind that, technically, other platforms implement ACL as
>> well, which could be problematic.
> Exactly my point, we are doing a platform-specific stuff there (uid
> comparison) is something that shouldn't be.


> Thanks for the offer Daniel, and I think adding those to win32-file
> will be great since ruby under Windows is blind in relation to ACLs.

I don't think we'll get them done in time for 1.3.0, though, so don't let it 
hold up this release. Something to consider for the next release perhaps.



More information about the Rubygems-developers mailing list