On Wed, Sep 17, 2008 at 8:51 PM, Phil Hagelberg <[EMAIL PROTECTED]> wrote:
> "Luis Lavena" <[EMAIL PROTECTED]> writes:
>
>> Yes, the same happened to me under Windows (user don't have write
>> access to C:/Ruby/lib/ruby/1.8/gems/**)
>>
>> Eric: what about using TMP for fetch actions? Is feasible?
>
> In trunk, this should fall back to "#{Gem.user_dir}/cache" if
> "#{Gem.dir}/cache" isn't writable. Are you seeing this in recent
> versions?
>No, I didn't push rubygems trunk to this production server so couldn't confirm and to be able to replicate the scenario require several ACLs changes. So I will trust the nice tests of RubyGems (btw, need to checkout latest and see if is working on both mswin32 and mingw32). Regards, -- Luis Lavena AREA 17 - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams _______________________________________________ Rubygems-developers mailing list Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
