You can clone with
HTTPS or Subversion.
I see that mail is tied to mime-types ~>1.16. I'm finding an increasing number of deps on mime-types 2.0.
Is there a roadmap for moving to mime-types 2.0?
Ok. So, since having to use mime-types 2.0 forces mail 2.2.7 (2.5.4 is current), is the best option is to build the gem locally overriding the gemspec?
Is there any strong opinion regarding when Mail will drop support for Ruby 1.8?
What I'm really asking is: would it be a worthwhile endeavour to investigate patching this?
FIX: bypass mail gem dependence mime's version
It's because the Mail gem depends on mime-types at ~> 1.16 and other gems have
moved on to 2.0. Relates to mikel/mail#641
This is holding more and more people back every day (or forcing them to overrule other dependencies, with unknown risks). Why not freeze 1.8 support here ? Those people/projects mostly live in the past anyway.
+1 on this issue, it's becoming a common problem with projects I work with. Surely this can be fixed ?
Any updates on this?
This is such a pain...
Upgrade to version 2.1 of mime-types
@ConradIrwin Tests pass locally after upgrading to the new version of mime-types. It looks like the ruby 1.8 builds are failing on your CI but the comments above lead me to believe that is expected/acceptable. Thoughts?
Would be great to get that resolved eventually.
This has been open over six months now. What is holding it up? Surely it can't be support for Ruby 1.8 which lost official support a year ago!?
#695, looks like no release planned.
2.6.1 is released with mime-types support up to 3 and is merged into Rails 4 through edge!