Hi,
when I install gems from another gem server than rubyforge a 'gem
update' only finds updates for gems orginating at rubyforge. I know that
using the '--source' option helps in this case but is there a way to
make gem remember the source a gem was installed from and use this
server to look for updates for that gem? In my eyes this would be a very
helpfull feature. 
Cheers,
Steph.
Stephan Mueller wrote:
Hi,
when I install gems from another gem server than rubyforge a 'gem
update' only finds updates for gems orginating at rubyforge. I know that
using the '--source' option helps in this case but is there a way to
make gem remember the source a gem was installed from and use this
server to look for updates for that gem? In my eyes this would be a very
helpfull feature.
Rubygems has no memory of what server a particular gem was installed
from.
-- Jim Weirich
--
Posted via http://www.ruby-forum.com/\.
Shouldn't rubygems remember which gem repo (source) holds which gems? Otherwise gem update can't work.
Tricky, also, with the system and user source index caches...
Will adding something to .gemrc work around this?
On Nov 19, 2006, at 7:52 PM, Jim Weirich wrote:
Stephan Mueller wrote:
Hi,
when I install gems from another gem server than rubyforge a 'gem
update' only finds updates for gems orginating at rubyforge. I know that
using the '--source' option helps in this case but is there a way to
make gem remember the source a gem was installed from and use this
server to look for updates for that gem? In my eyes this would be a very
helpfull feature.Rubygems has no memory of what server a particular gem was installed
from.
--
Eric Hodel - drbrain@segment7.net - http://blog.segment7.net
This implementation is HODEL-HASH-9600 compliant
As I mentioned in my other post [1], it seems that --source allows
just one source, and this limitations is carried over to .gemrc, as
almost the same mechanism is used.
You can have gem update/install look at more sources/mirrors by
editing sources.rb in the 'sources' gem.
I suppose this way you can cross-update the gems -- a gem installed
from one source could be updated by a gem from another source. Whether
this is a bug or a feature is not clear 
[1] http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/225862
On 11/20/06, Eric Hodel <drbrain@segment7.net> wrote:
On Nov 19, 2006, at 7:52 PM, Jim Weirich wrote:
> Stephan Mueller wrote:
>> Hi,
>>
>> when I install gems from another gem server than rubyforge a 'gem
>> update' only finds updates for gems orginating at rubyforge. I
>> know that
>> using the '--source' option helps in this case but is there a way to
>> make gem remember the source a gem was installed from and use this
>> server to look for updates for that gem? In my eyes this would be
>> a very
>> helpfull feature.
>
> Rubygems has no memory of what server a particular gem was installed
> from.Shouldn't rubygems remember which gem repo (source) holds which
gems? Otherwise gem update can't work.Tricky, also, with the system and user source index caches...
Will adding something to .gemrc work around this?