WARNING: no rubyforge_project specified
WARNING: deprecated autorequire specified
no rubyforge_projectone doesn't check to see if you've already declared a rubyforge value for homepage:
s.homepage = "http://rubotz.rubyforge.org"
s.rubyforge_project = "rubotz"
But if you don't do both, you get either a
no homepage specifiedor a
no rubyforge project specifiedwarning.
deprecated autorequirewarning is a little weirder. It's pretty obvious that you can just use
requireinstead; what's less obvious is why you have
autorequireinstead. My gemspec was initially generated by Hoe, so like with any generated code, there's a certain air of mystery involved. You have to wonder if
requireis enough, because if it was enough, why did
autorequireexist in the first place?
Fortunately, Google can find you an excellent explanation from Jim Weirich:
The autorequire feature is a holdover from the days when regular requires didn't work in rubygems. It avoided the need to do a require_gem *and* a regular require. Since the regular require is all that is needed today, autorequire is a holdover from the past.
Long story short, just use