source :rubygems use HTTPS instead of deprecating? #2406

Closed
sethvargo opened this Issue Mar 17, 2013 · 1 comment

Comments

Projects
None yet
2 participants

Hey all,

On the current version of Rubygems, specifying the source as a symbol throws a deprecation error because the symbol is tied to http, not https. That's a really breaking change and is causing a lot of confusion because using the symbol has always been a more recommended way (in all the tutorials I've seen). Would it be possible to use https for the symbol instead of deprecating it all-together? I totally see the value in using https, and we always should have been using https, but it seems a little backward to remove the "shorthand" version of source :rubygems. Thoughts?

Stemmed from: RiotGames/berkshelf#417 (comment)

Owner

indirect commented Mar 17, 2013

I'm sorry, but how is printing a deprecation warning a breaking change? For a discussion of why the symbol shorthand is being removed instead of silently changed to HTTPS, please see #2357, #2345, #1587, and #1585.

@indirect indirect closed this Mar 17, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment