To list the available DevKit versions and current default, invoke rake devkit:ls. For example:. Skip to content. Star 1. RubyInstaller for Windows - Build recipes rubyinstaller.
BSDClause License. Branches Tags. Could not load branches. Could not load tags. Latest commit. Git stats commits. That might be an option. The funny thing is, that usually the more you wait, the more you are afraid and the bigger the gap is. Working with legacy code it is usually hard to even adopt and enforce constructs which would eventually shrink the gap. Also, there is this strange myth of R1. But if you would spent the amount of time you spent with the backporting on conversion to R1.
In my previous company, we switched from R1. Of course that was success story because of wonderful RubyInstaller : Vit. Actually, you're forking Ruby and adding a patch and aiming to distribute that version without "proof" that there is a real need for it.
So far, you've been the first and only requesting this. You haven't look at the alternatives that we mention and the requirements of those. AFAIK these were more simpler to implement and follow than what you have done. Yet still, you mention "enhancing our gems", which is not what you have accomplish here. I know this line is not targeted at me.
When I think about consistency, I think on what you're doing with the fork and you're going the opposite direction. You mention your application is used in dunno how many places. So if the IT department of that place wanted to check what you have done, or a possible problem they could solve, the will find references to Ruby for Windows and RubyInstaller in your fork, and direct all the issue, grief or whatever to us first google result.
Then we will need to deal with the burden of a fork that might differ in dunno how many ways because is not packaged by us or signed by us You talk about enterprise and consistency, yet still this single point defeat your statement. I'll sound like a broken record, but over the past 15 years I worked in the video broadcast industry and let me tell you, every second you loose there, thousands of dollars are lost.
I learnt there think of all the possible scenarios things will fail. And most of the time, when I look to an OSS library, apply one single scenario, it breaks. Some people consider me a magnet to bugs. I try to apply the same principles I learnt doing that to my OSS development, and so far they worked up to my expectations. Some people will disagree with my point of view in relation to RubyInstaller, but I believe, while slow and steady, we accomplish a lot.
Now, I might not have specific experience in dotNET or Java corporate environments, but what I do know, still applies to all of them.
This is not a mine is bigger than yours response, but I want to put a end to this thread as is not been productive at all for any of us. No point that you can possible reiterate that wasn't discussed before needs to be presented or discussed further.
Sorry, it was irony It was not about throwing out the code but about keeping with upstream. Two completely different cases. I could demonstrate on more examples and wrong decision which were unfortunately taken during the years I spent in previous company. But that is long story and off-topic. That is a lot of noise, if you ask me. I think you do not understand my problem. I agree. An easy task. They work perfectly well on Linux. That is wonderful, but are you going to make gd2 functioning for 1.
This is the same example as keeping you code with upstream. But the longer we had worked with QT, the more we have to workaround QT inabilities. We never contributed anything upstream and it led just to diversion from compatibility with upstream.
At the end, although the application was QT based, I would never tried it to compile it on Linux nor run it. Seems that my attempt to put an end to this thread didn't succeed, but. Neither authors mention what dependencies their libraries require and so many other conditions not been considered when releasing code in the wild. And other authors simple don't care. So, if you aim your application works on all the platforms, learn the platforms. Learn the Windows API if is required which is for your GD2 issue and fix it, or create a new library that correct the GD2 issue and release it as replacement, so your Linux and Windows version both use the same codebase.
If you want to accomplish that for your application, it is time you and your team get your hands dirty. Ruby 1. Zeno R. Reply to author. Report message as abuse. Show original message. Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message. I believe there are many people out there that want Ruby 1.
Oniguruma takes care of regular expressions. I know Ruby 1. But I believe there are actually many people who want Ruby 1. Now it would be great if there would be a one-click installer for that so that the user does not have to Patch Ruby 1.
So how about providing a separate package of Ruby1. Are you interested or do you know somebody who could do that? I am also interested in providing the work to anybody who needs it. Thank you for your Feedback. Best Zeno. Gordon Thiesfeld. Hi Jon Thanks for the reply.
On 6 Jan. Dear Gordon Thank you for your reply. Hopefully :. Luis Lavena. I will double-check those settings. On 7 Jan. Thank you very much! Ok this compiled without a single error! But now I need to confirm it. This seems very suspicious to me. I need to find that out now.
Learn more. Steps for Upgrading Ruby Installer for Windows from 1. Asked 10 years, 11 months ago. Active 10 years, 11 months ago. Viewed 1k times. Improve this question. Paul Paul 43 1 1 silver badge 4 4 bronze badges. Add a comment. Active Oldest Votes. RubyInstaller and One-Click differ a lot in technical aspects, which could affect your upgrade path override or install on top of it Also, old One-Click Installer had the bad habit of removing your gems and customizations, something that could make you pull your hair.
Hope this helps. Improve this answer. Luis Lavena. Andrei S Andrei S 6, 5 5 gold badges 35 35 silver badges 52 52 bronze badges.
0コメント