Misc #9006: build and host binary rubies

• Status: Rejected
• Assignee: hsbt (Hiroshi SHIBATA)

[mpapis (Michal Papis)]

I wanted to ask ruby to take back the binary rubies, currently they are maintained as part of RVM.

The build is done using: https://github.com/rvm/rvm-binary

The binaries are hosted: https://rvm.io/binaries/

I'm also fine with slow migration where I continue to build the binaries and they are hosted at: http://ftp.ruby-lang.org/pub/ruby/

[luislavena (Luis Lavena)]

=begin
Hello Michal,

Platform binaries is a great thing, however I noticed that your username leaked into the generated (({rbconfig})) file:

$ gem env paths
/Users/mpapis/.rvm/gems/ruby-2.0.0-p247

I believe this is caused by the patching of (({ENV["GEM_HOME"]})) and ((|PATH|)) at the beginning of each script?

Cheers.

=end

[mpapis (Michal Papis)]

oh that's my bad and easy thing to fix, thanks for heads up! (I guess the binaries can be build fresh if/when Ruby decides to take over the process)

[hsbt (Hiroshi SHIBATA)]

Hi, Michal

I'm ok for your suggestion. but I have two questions.

1. How to upload/sync rvm package files?
2. How to escalate package issue?

[hsbt (Hiroshi SHIBATA)]

• Assignee set to hsbt (Hiroshi SHIBATA)

[mpapis (Michal Papis)]

=begin
This is what I wanted to discuss, right now the whole process is controlled in rvm, so the builds are done and uploaded(scp) by me and the issues are initially handled at rvm bug tracker, I forward them here when needed.

There are 3 steps I can distinguish for the process (each is optional):

(1) The build is still done by me and the binaries are copied from ((URL:https://rvm.io/binaries)) to ((URL:http://ftp.ruby-lang.org/pub/ruby/binaries))
(2) The builds are done by ruby team using rvm and uploaded directly to ftp.ruby-lang.org
(3) The build process is done without rvm and binaries are uploaded to ftp.ruby-lang.org

I can be in full assistance as long rvm is involved, not sure about my time if rvm is not used.

As to handling package issues - they will be most likely reported first to the tool used for installing the binary ruby and only re-posted to ruby team when needed. See ((<rvm#2189|URL:https://github.com/wayneeseguin/rvm/issues/2189>)) - ((<ruby#8879|URL:https://bugs.ruby-lang.org/issues/8879>)) for example.
=end

[postmodern (Hal Brodigan)]

rvm-bin is definitely the most immediately viable solution. In the future, you should consider using something like Gitian for reproducable builds. http://gitian.org/

[shan (Shannon Skipper)]

It seems to be a good time to make the RVM-provided binaries official by hosting them at http://ftp.ruby-lang.org/pub/ruby/binaries since both ruby-install (chruby) and ruby-build (rbenv) are looking to support installing them. RVM has been using them for some time and people have been installing them directly. It would make it easier for folk to find them and for the installation tools to rally behind them if they were hosted officially.

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Rejected

I've been shipped the binary ruby named snaps.

https://snapcraft.io/ruby