[ruby-core:57973] [ruby-trunk - misc #9006] build and host binary rubies

Issue #9006 has been updated by 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

----------------------------------------
misc #9006: build and host binary rubies
https://bugs.ruby-lang.org/issues/9006#change-42549

Author: mpapis (Michal Papis)
Status: Open
Priority: Low
Assignee: hsbt (Hiroshi SHIBATA)
Category: 
Target version: 


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/


-- 
http://bugs.ruby-lang.org/