mime-type 2.0 support

[auxbuss]

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?

[ConradIrwin]

It probably just needs to be tested and then committed. Pull requests
welcome :)

On Monday, December 2, 2013, Marc Cooper wrote:

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?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/641
.

[jeremy]

2.0 drops Ruby 1.8 support, so we can bump when mail drops support also.

On Mon, Dec 2, 2013 at 9:38 AM, Conrad Irwin notifications@github.comwrote:

It probably just needs to be tested and then committed. Pull requests
welcome :)

On Monday, December 2, 2013, Marc Cooper wrote:

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?

—
Reply to this email directly or view it on GitHub<
https://github.com/mikel/mail/issues/641>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/641#issuecomment-29633375
.

[auxbuss]

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?

[jeremy]

That, or relax your other libs' dependency on mime-types 2.0.

On Mon, Dec 2, 2013 at 11:21 AM, Marc Cooper notifications@github.comwrote:

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?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/641#issuecomment-29643181
.

[parndt]

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?

[NielsKSchjoedt]

+1

[pca2]

+1

[oliver-k-yeh]

+1

[vdaubry]

+1

[ameuret]

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.

[opensourceame]

+1 on this issue, it's becoming a common problem with projects I work with. Surely this can be fixed ?

[jtescher]

Any updates on this?

[NielsKSchjoedt]

This is such a pain...

[heidi]

@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?

[maxrice]

+1

[arp]

Would be great to get that resolved eventually.

[ldiqual]

+1

[opensourceame]

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!?

[carsonreinke]

#695, looks like no release planned.

[bf4]

2.6.1 is released with mime-types support up to 3 and is merged into Rails 4 through edge!