This is interesting: http://www.rubyinside.com/rip-ruby-packaging-system-1837.html How will this affect Ruby for Windows? Will it make life better? Charles
On Mon, Jun 15, 2009 at 6:20 AM, Charles Roper<reachme at charlesroper.co.uk> wrote:> This is interesting: > > http://www.rubyinside.com/rip-ruby-packaging-system-1837.html > > How will this affect Ruby for Windows? Will it make life better? >Is quite interesting how Chris used RUBYLIB and PATH, but the usage of symlinks is not good for us on Windows. Unless they change or move to a config file based selector for active environments, we would be out of luck with it. For other stuff (like RUBYLIB and PATH), I''ve pointed Chris to take a look to Pik on how to alter current processor / shell environment ;-) One important point is that RIP does not handle native extensions or anything, is more for libraries. In that front RubyGems is light years advanced. Regards, -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry
Luis Lavena wrote:> On Mon, Jun 15, 2009 at 6:20 AM, Charles > Roper<reachme at charlesroper.co.uk> wrote:>>> http://www.rubyinside.com/rip-ruby-packaging-system-1837.html >> >> How will this affect Ruby for Windows? Will it make life better? > > Is quite interesting how Chris used RUBYLIB and PATH, but the usage of > symlinks is not good for us on Windows.It would be OK for Vista/Win7 users, just not for pre-Vista users, surely (of which there are a lot still, I know)? Charles
On Tue, Jun 16, 2009 at 9:49 AM, Charles Roper<reachme at charlesroper.co.uk> wrote:> Luis Lavena wrote: >> >> >> Is quite interesting how Chris used RUBYLIB and PATH, but the usage of >> symlinks is not good for us on Windows. > > It would be OK for Vista/Win7 users, just not for pre-Vista users, surely > (of which there are a lot still, I know)? >For you to use mklink you need symlink permission, which is not available to all user, only ones with administrative permissions. Try this: Increase the UAC to the maximum, and then try to create a symlink on a standard command prompt, you will get a permission denied. That''s why I''ve copied elevated form the powertoys of vista to my repository: http://github.com/luislavena/binfiles/tree/master Using elevated I can call mklink with the UAC prompt. Anyhow, I believe that a simple yaml file could easily replace the symlink, since it''s only used for the current and active environment, nothing else. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry