#22406: [Ruby] New Official gem repository - GemCutter.org ---------------------------------+------------------------------------------ Reporter: dreamcat4@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 1.8.1 Keywords: | Port: ---------------------------------+------------------------------------------ Comment(by dreamcat4@…): We would be better off implementing this as a wrapper ontop of Ticket #22530. And then replacing the existing rubygems fetch method with a similar wrapper. This will allow more freedom to specify alternate gem source(s). What's not clear is whether we need to implement some failover or a priority list. Ie if a gem migrates from rubyforge to gemcutter. We might just update those manually and avoid implement such a complex priorities mechanism. -- Ticket URL: <http://trac.macports.org/ticket/22406#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#22406: [Ruby] New Official gem repository - GemCutter.org ----------------------------------+----------------------------------------- Reporter: dreamcat4@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: | ----------------------------------+----------------------------------------- Changes (by kimuraw@…): * status: new => closed * resolution: => fixed Comment: gemcutter now provides gems as rubygems.org and macports' portgroup ruby supports rubygems.org with keyworkd "rubygems". ex) port:rb19-nanoc3 {{{ PortSystem 1.0 PortGroup ruby 1.0 ruby.setup nanoc3 3.1.3 gem {} rubygems ruby19 }}} I think we can close this ticket as "fixed". -- Ticket URL: <https://trac.macports.org/ticket/22406#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS