I’ve just reinstalled linux (9.10) and am trying to match my gem
environment to our server’s. I’m having a problem with will_paginate.
On the server, under gem list, i have “mislav-will_paginate (2.3.6)”.
So, i’m trying to install that locally. Following the instructions on
the will_paginate page, http://wiki.github.com/mislav/will_paginate,
i’ve installed it.
But, it shows up on my gem list as simply “will_paginate”, and rails
complains because it’s expecting mislav-will_paginate.
So, can anyone point me at where i can install mislav-will_paginate, so
that it will actually show up on my gem list as mislav-will_paginate
instead of will_paginate?
I feel like i’m being dumb and missing something obvious here…grateful
for any help.
That will tell rails to look for the will_paginate library inside the
mislav-will_paginate gem, and you should be fine.
Max W. wrote:
I’ve just reinstalled linux (9.10) and am trying to match my gem
environment to our server’s. I’m having a problem with will_paginate.
On the server, under gem list, i have “mislav-will_paginate (2.3.6)”.
So, i’m trying to install that locally. Following the instructions on
the will_paginate page, http://wiki.github.com/mislav/will_paginate,
i’ve installed it.
But, it shows up on my gem list as simply “will_paginate”, and rails
complains because it’s expecting mislav-will_paginate.
So, can anyone point me at where i can install mislav-will_paginate, so
that it will actually show up on my gem list as mislav-will_paginate
instead of will_paginate?
I feel like i’m being dumb and missing something obvious here…grateful
for any help.
I already have that line as it happens -
config.gem ‘mislav-will_paginate’, :version => ‘~> 2.3.2’, :lib =>
‘will_paginate’, :source => ‘http://gems.github.com’
I think the problem is that i don’t have the mislav-will_paginate gem, i
have the will_paginate gem. I could modify the above line to point to
will_paginate instead of mislav-will_paginate, but then i’ll be out of
sync with the server, which i don’t want to do.
gem list mislav-will_paginate --remote
*** REMOTE GEMS ***
mislav-will_paginate (2.3.11)
em list will_paginate --remote
*** REMOTE GEMS ***
will_paginate (2.2.2)
My guess is that you do have mislav-will_paginate installed, since
will_paginate is only up to v2.2.2, but you’ve got an older version.
Why don’t you try:
What’s odd is that i’m installing it following the instructions on the
mislav-will_paginate homepage, wherer they say to do “gem install
will_paginate”, after setting the gem source. So, it’s like i’m
installing something that is to all practical purposes the mislav
version, but it’s not called mislav, and that’s my problem.
One more point. You said that you followed the instructions for
install - there are three different paths there and I know for a fact
that the “gem install…” version will give you “mislav-
will_paginate”. If, however, you build from a tar (or use git clone)
the gemspec delivered will build a gem named “will_paginate”.
complains because it’s expecting mislav-will_paginate.
So, can anyone point me at where i can install mislav-will_paginate, so
that it will actually show up on my gem list as mislav-will_paginate
instead of will_paginate?
I feel like i’m being dumb and missing something obvious here…grateful
for any help.
Hi, if you haven’t heard github.com is moving away from being a gem
host,
you should do the following to install will_paginate:
I just checked and will_paginate v2.2.2 is being served by http://gems.rubyforge.org while mislav-will_paginate v2.3.11 is being
served by http://gems.github.com. Conrad’s point is good for the
future but right now you should check your .gemrc file (that’s
~/.gemrc).
One more point. You said that you followed the instructions for
install - there are three different paths there and I know for a fact
that the “gem install…” version will give you “mislav-
will_paginate”. If, however, you build from a tar (or use git clone)
the gemspec delivered will build a gem named “will_paginate”.
Rick, i did the “gem install” path: to quote
The will_paginate gem is hosted on Gemcutter. Add it to your gem sources
(once per machine):
What’s odd is that i’m installing it following the instructions on the
mislav-will_paginate homepage, wherer they say to do “gem install
will_paginate”, after setting the gem source. So, it’s like i’m
installing something that is to all practical purposes the mislav
version, but it’s not called mislav, and that’s my problem.
Please note that ‘gem tumble’ will update your .gemrc file so that http://gemcutter.org appears first in the list of Ruby gem hosts.
-Conrad
Hi Conrad
I’d not heard of ‘gem tumble’…i just tried it and got “unknown command
tumble”. I’m using gem v 1.3.5
The will_paginate gem is hosted on Gemcutter. Add it to your gem sources
When you say you know for a fact, then either it’s changed since you did
it, or something weird and unexpected happened when i did it.
I wouldn’t recommend the above because it doesn’t make gemcutter.org
the primary Rubygems host. One should do the following:
What’s odd is that i’m installing it following the instructions on the
mislav-will_paginate homepage, wherer they say to do “gem install
will_paginate”, after setting the gem source. So, it’s like i’m
installing something that is to all practical purposes the mislav
version, but it’s not called mislav, and that’s my problem.
Please note that ‘gem tumble’ will update your .gemrc file so that http://gemcutter.org appears first in the list of Ruby gem hosts.
It appears that the paginate gem served up from gemcutter is, in fact,
built from the current mislav-will_paginate version2.3.11. The
confusion regarding the name stems from:
The gemspec distributed from the git://…mislav/will_paginate site
builds a gem named “will_paginate” not “mislav-will_paginate”. There
are other problems (I18n related) with the gemspec as well.
The documentation distributed with the gem “mislav-will_paginate”
clearly states that you should remove the old gem named
“will_paginate”.
I expect that you would see identical results with either the github
or the gemcutter version of the gem. I’m going to follow Conrad’s
direction to gemcutter.
The gemspec distributed from the git://…mislav/will_paginate site
builds a gem named “will_paginate” not “mislav-will_paginate”. There
are other problems (I18n related) with the gemspec as well.
cool, glad it’s not just me that’s confused then. I never understood
why the gem was prefixed with mislav- in the first place tbh.
The gemspec distributed from the git://…mislav/will_paginate site
builds a gem named “will_paginate” not “mislav-will_paginate”. There
are other problems (I18n related) with the gemspec as well.
cool, glad it’s not just me that’s confused then. I never understood
why the gem was prefixed with mislav- in the first place tbh.
Github prefixed generated gems with username and hyphen.
The gemspec distributed from the git://…mislav/will_paginate site
builds a gem named “will_paginate” not “mislav-will_paginate”. There
are other problems (I18n related) with the gemspec as well.
cool, glad it’s not just me that’s confused then. I never understood
why the gem was prefixed with mislav- in the first place tbh.
Github prefixed generated gems with username and hyphen.
That seems fine if it’s a branching kind of deal and there’s lots of
different alternatives to a particular gem. But, mislav-will_paginate
seems to be the ‘official’ will_paginate, so the name change seems
superfluous at best and confusing at worst. Although, maybe at the time
it was renamed it wasn’t clear that it was going to be the ‘official’
version, which is why it’s now back to being just will_paginate again i
guess.
Anyway, who am i to tell the gem builders what to do
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
