Per-user gems should not be the default. In RubyInstaller (mingw MRI), as well as MRI on Linux, and I believe OS X, system-wide gems are the default. This, of course, would require elevation (sudo gem install xxx).
-- Will Green http://hotgazpacho.org/ On Mon, Jan 25, 2010 at 7:58 PM, Shri Borde <shri.bo...@microsoft.com>wrote: > Just realized that setting GEM_PATH will affect MRI too which would be a > problem. So there will have to be some other way to implement the per-user > IronRuby-specific location for gems. Assuming we can figure this out, the > question still is if the per-user gems model sounds good… > > > > *From:* ironruby-core-boun...@rubyforge.org [mailto: > ironruby-core-boun...@rubyforge.org] *On Behalf Of *Shri Borde > *Sent:* Monday, January 25, 2010 4:47 PM > > *To:* ironruby-core@rubyforge.org > *Subject:* Re: [Ironruby-core] "igem install rake" raise an > System.UnauthorizedAccessException (Windows 7) > > > > Jim and I were discussing the desired behavior, and it is a choice between > security and convenience. > http://ironpython-urls.blogspot.com/2009/10/distributing-ironpython-packages.htmlhas > information on how Python is dealing with the admin issue. Packages (the > equivalent of gems) are installed to a per-user location. The IronRuby > equivalent would be that every user has to install his/her own set of gems, > and could be implemented by setting the GEM_PATH environment variable for > the user to point to something like %USERPROFILE%. Any objection to this > behavior? > > > > *From:* ironruby-core-boun...@rubyforge.org [mailto: > ironruby-core-boun...@rubyforge.org] *On Behalf Of *Shri Borde > *Sent:* Monday, January 25, 2010 1:55 PM > *To:* ironruby-core@rubyforge.org > *Subject:* Re: [Ironruby-core] "igem install rake" raise an > System.UnauthorizedAccessException (Windows 7) > > > > Btw, c:\ironruby will still need admin priviledges to install to, right? > > > > Does the one-click installer make the gem folder writable to all users (or > atleast all Admin users)? What about on *nix? Without making the gem folder > writable, “igem install” will still fail. Making the folder writable to all > users is a security hole, and ideally RubyGems will support a way to install > to a per-user location, or elevate permission otherwise. I believe you need > to use “sudo gem install” on *nix. > > > > *From:* Shri Borde > *Sent:* Monday, January 25, 2010 1:42 PM > *To:* ironruby-core@rubyforge.org > *Subject:* RE: [Ironruby-core] "igem install rake" raise an > System.UnauthorizedAccessException (Windows 7) > > > > Added a comment to the workitem… > > > > *From:* ironruby-core-boun...@rubyforge.org [mailto: > ironruby-core-boun...@rubyforge.org] *On Behalf Of *Ivan Porto Carrero > *Sent:* Monday, January 25, 2010 12:43 PM > *To:* ironruby-core@rubyforge.org > *Subject:* Re: [Ironruby-core] "igem install rake" raise an > System.UnauthorizedAccessException (Windows 7) > > > > Program files is a protected location and contains a space in the path. I > couldn't find a workitem. But all the problems would be solved > by mimicking jruby and ruby's way and just putting it in C:\ironruby. > > > > This workitem is related though > > http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=2969 > > > > --- > Met vriendelijke groeten - Best regards - Salutations > Ivan Porto Carrero > Blog: http://flanders.co.nz > Twitter: http://twitter.com/casualjim > Author of IronRuby in Action (http://manning.com/carrero) > > On Mon, Jan 25, 2010 at 8:30 PM, Shri Borde <shri.bo...@microsoft.com> > wrote: > > Ivan, do you remember what the known issue is? I can’t remember seeing a > discussion about UnauthorizedAccessException. Just making sure that the bug > is really being tracked > > > > *From:* ironruby-core-boun...@rubyforge.org [mailto: > ironruby-core-boun...@rubyforge.org] *On Behalf Of *Thibaut Barrère > *Sent:* Monday, January 25, 2010 7:21 AM > *To:* ironruby-core@rubyforge.org > *Subject:* Re: [Ironruby-core] "igem install rake" raise an > System.UnauthorizedAccessException (Windows 7) > > > > it's a known issue that should be fixed in the next release, AFAIK > > > > > Thanks Ivan, > > > > -- Thibaut > > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
