From: Eric Wong Date: 2017-12-16T01:44:59+00:00 Subject: [ruby-core:84299] Re: [Ruby trunk Bug#14189] Webrick 1.4.0. release requires unreleased ruby version 2.5.0dev Greg.mpls@gmail.com wrote: > Eric, > > Looking over 61155, it does seem rather odd to constrain updates to WEBrick to ruby >= 2.5 for two warnings. Also, I believe WEBrick is the only gem affected by it. Don't know what your thoughts are... I am of two minds; for my projects which were never in ruby-core, I still support 1.9.3 (even if ruby-core does not). But one appeal of working on stdlib is being able to use (and test) new Ruby features right away. > Also, re users not needing to install WEBrick, from over in the RubyInstaller repo, the first thing many people do with a Ruby install is `gem update` (which is why I asked a while ago about a digest gem). If WEBrick can maintain compatibility with 2.3 forward, it would probably help a lot of support people... The thing is, ruby 2.4 and earlier do not have webrick installed as a gem by default; it wasn't a default gem until 2.5. So "gem update" for a 2.4 user should still never see this unless they willingly had an ancient 1.3.1 installed. I'm not sure what hsbt and the rest of ruby-core wants to do. Personally, I do not like version guards, either. Unsubscribe: