Closed jgaskins closed 11 years ago
Oh, right. :-) Well, I understand how this passed on my machine (I hadn't removed the gem), but how does it pass on Travis? Doesn't it get a fresh bundle every build?
Ah, it's still a dependency of dependencies.
➜ virtus git:(remove-backports-gem) gem uninstall backports
You have requested to uninstall the gem:
backports-3.3.0
abstract_type-0.0.5 depends on [backports (>= 3.0.3, ~> 3.0)]
adamantium-0.0.7 depends on [backports (>= 3.0.3, ~> 3.0)]
coercible-0.2.0 depends on [backports (>= 3.1.0, ~> 3.0)]
equalizer-0.0.5 depends on [backports (>= 3.0.3, ~> 3.0)]
mutant-0.2.20 depends on [backports (>= 3.0.3, ~> 3.0)]
yardstick-0.9.5 depends on [backports (>= 3.0.3, ~> 3.0)]
If you remove this gems, one or more dependencies will not be met.
Continue with Uninstall? [Yn]
Alrighty, removed the require. Until everyone else removes their dependency on it it'll still be there, but at least this will remove the dependency from Virtus itself. :-)
Thanks Jamie! We are supposed to remove ruby 1.8 support from other projects in June when ruby core team drops it too. Then backports dep will be gone for good :)
:+1: for GCing dependencies!
@solnic Hi! Great change!
Still one wish. virtus
depends on coercible
which depends on backports
.
So installing virtus
still grub this gem as dependecy.
In master coercible
does not rely on backports
any more. Can we release new version of coercible
and bump virtus?
@randx yes and in fact just yesterday I noticed the same thing and realized I need to push a new release of coercible along with virtus 1.0.1
@solnic awesome! Thank you
Since 1.8 support was removed in 845b36ec36bd82c2f49063c9d3c6fd52a0b54864, it doesn't appear that backports is necessary anymore. I ran rake under 1.9.2 and it gives no failures, so that's a good sign. Is there anything else I need to check here?