On Mon, Jan 25, 2010 at 1:55 PM, Jim Deville <jdevi...@microsoft.com> wrote:
> If you need the IronRuby folder in the "right" location, then require your > users to use the installer with default options. However, even then, you are > requiring your users to go through the greater issue of installing IronRuby > and all of your required gems. You are also requiring them to keep up with > your versions if you choose to update. I would expect people to include the > IronRuby dll's and the required ruby libraries with their application, just > like they would do with .NET libraries. Then the setup isn't a problem since > it is only setting up the app. Right. This isn't .NET, so it shouldn't behave like .NET. If developers are going to use Ruby, then they need to learn to use Ruby. You want to solve a problem, but I'm not seeing that a problem exists. The gem issue seems to be sorted soon with the dash_s addition. Other problems, such as C extensions, are problems for any non-MRI / Ruby 1.9 implementation, and everyone is working on how to sort that out. IronRuby is still in development, and the team is doing a terrific job getting it there. You're going to have to help people shift their expectations to get them onto IronRuby. I don't expect (and don't want) IronRuby to work like C# or VB.NET in Visual Studio. It's a totally different animal altogether, which is what makes it so fun to use! So, what exactly is the problem you want to solve? And please don't mention config settings (already an issue for other .NET libraries), ENV variables (already optional in MRI), or gem naming issues, as these aren't related to IronRuby. Regards, Ryan
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
