According to the stats on rubyforge and gemcutter, it looks like a few users are still installing the old FakeWeb versions of the gem.
We could probably ask to have them removed outright, since the pre-1.2.0 gem versions are still available as "fakeweb" gems.
I think a nicer solution would be to do a final release in the 1.1.x series that uses RubyGems's post-install hook to print out a note about the FakeWeb -> fakeweb change. Maybe add a warning when that version is required, too. It might be annoying, but the exact same versions of the gems exist under the fakeweb name, so switching should be pretty easy for anyone still using the old gems.
According to the stats on rubyforge and gemcutter, it looks like a few users are still installing the old
FakeWebversions of the gem.We could probably ask to have them removed outright, since the pre-1.2.0 gem versions are still available as "fakeweb" gems.
I think a nicer solution would be to do a final release in the 1.1.x series that uses RubyGems's post-install hook to print out a note about the
FakeWeb->fakewebchange. Maybe add a warning when that version is required, too. It might be annoying, but the exact same versions of the gems exist under thefakewebname, so switching should be pretty easy for anyone still using the old gems.