What do you mean about yanking these gems? Do you mean yanking all the versions?
I'm not sure this is a good idea - usually only particular versions of the gems are yanked because they have some critical problem. And if you only yank the last version, then you can still install the version before that. I'm pretty sure you can still use firewatir with some older version of Firefox successfully. There might be still some legacy projects depending on these particular gems for whatever reason. A better idea would be to release a newer version of these gems with having a message similar to the lines of "this gem is now deprecated, use watir instead or if you really need this gem, then the previous version might work for you." when loading them. Do you see any problem with these gems? Is there a lot of confusion happening because of them? Jarmo On Sat, Feb 8, 2014 at 11:55 PM, Željko Filipin <[email protected]>wrote: > Hi, > > I am thinking about yanking deprecated watir gems[1][2] from rubygems.org. > Anybody thinks that is a bad idea? > > I am not sure if anybody is using operawatir[3], I have asked Andreas[4]. > > Željko > -- > 1: https://rubygems.org/gems/firewatir > 2: https://rubygems.org/gems/safariwatir > 3: https://rubygems.org/gems/operawatir > 4: https://twitter.com/zeljkofilipin/status/432270609385390080 > > _______________________________________________ > Wtr-development mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/wtr-development >
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
