Update installed gems

Dale Martenson · Aug 9, 2005

I build my own gems as a way to distribute a variety of utilities where
I work. What is the best way to install updates?

If I distribute a new gem file, provided by email/ftp/web how can a user
install the update? Should they just re-install? "gem update <blah>"
doesn't seem to have a "--local" option. If you place the file in your
current directory, it seems to be ignored and I am not sure how to
specify a gem update file. While "gem install" will automatically look
both for the gem locally and remotely, "gem update" doesn't.

Maybe, this is a bad question since "gem update" is meant to look for
updates that are not locally available. But this doesn't seem consistent
with the way "gem install works".

How difficult is it to implement a simple gem server?

Ezra Zygmuntowicz · Aug 9, 2005

I build my own gems as a way to distribute a variety of utilities
where I work. What is the best way to install updates?

If I distribute a new gem file, provided by email/ftp/web how can a
user install the update? Should they just re-install? "gem update
<blah>" doesn't seem to have a "--local" option. If you place the
file in your current directory, it seems to be ignored and I am not
sure how to specify a gem update file. While "gem install" will
automatically look both for the gem locally and remotely, "gem
update" doesn't.

Maybe, this is a bad question since "gem update" is meant to look
for updates that are not locally available. But this doesn't seem
consistent with the way "gem install works".

How difficult is it to implement a simple gem server?

$ gem_server
On the command line. This serves you rdoc documentation and it can
act as a local gem repository server. I've never set up the local
repo so perhaps someone else can chime in./ But it already has
features to do exactly what you want.
HTH-
-Ezra Zygmuntowicz
Yakima Herald-Republic
WebMaster
509-577-7732
(e-mail address removed)

Dale Martenson · Aug 9, 2005

---- Original message from Ezra Zygmuntowicz on 8/9/2005 12:28 PM:

$ gem_server
On the command line. This serves you rdoc documentation and it can
act as a local gem repository server. I've never set up the local
repo so perhaps someone else can chime in./ But it already has
features to do exactly what you want.

I will give that a try, but it seems like it is meant to serve your
installed gems. If someone wanted to host and variety of gems (different
versions of gems -- stable, bleeding edge, etc.), I don't think
"gem_server" is the answer. Any ideas what is? Or am I understanding
this incorrectly.

Chad Fowler · Aug 10, 2005

=20
---- Original message from Ezra Zygmuntowicz on 8/9/2005 12:28 PM:
=20
I will give that a try, but it seems like it is meant to serve your
installed gems. If someone wanted to host and variety of gems (different
versions of gems -- stable, bleeding edge, etc.), I don't think
"gem_server" is the answer. Any ideas what is? Or am I understanding
this incorrectly.
=20
=20

Hi. gem_server can definitely do what you want. You can serve gems
from an alternate directory (with the -d param) if you want to include
a lot of bleeding edge gems that you don't want "installed" on the
host system. Also, if you look in the rubygems distribution under the
"bin" directory, you'll find generate_yaml_index.rb, which you can
use to create a static yaml file that you could serve with your web
server of choice. So you'd have:

http://yourserver.whatever.org/yaml
and
http://youserver.whatever.org/gems/mygems.gem

If you have that structure available, you can serve gems from a
normal web server.

--=20
Chad Fowler
http://chadfowler.com
http://rubycentral.org=20
http://rubygarden.org=20
http://rubygems.rubyforge.org (over 700,000 gems served!)

Dale Martenson · Aug 10, 2005

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
---- Original message from Chad Fowler  on 8/10/2005 6:41 AM:
<blockquote cite="(e-mail address removed)"
type="cite">
</pre>
<blockquote type="cite">
<pre wrap="">---- Original message from Ezra Zygmuntowicz on 8/9/2005 12:28 PM:

</pre>
<blockquote type="cite">
<pre wrap="">On Aug 9, 2005, at 10:18 AM, Dale Martenson wrote:

</pre>
<blockquote type="cite">
<pre wrap="">I build my own gems as a way to distribute a variety of utilities
where I work. What is the best way to install updates?

If I distribute a new gem file, provided by email/ftp/web how can a
user install the update? Should they just re-install? "gem update
<blah>" doesn't seem to have a "--local" option. If you place the
file in your current directory, it seems to be ignored and I am not
sure how to specify a gem update file. While "gem install" will
automatically look both for the gem locally and remotely, "gem
update" doesn't.

Maybe, this is a bad question since "gem update" is meant to look
for updates that are not locally available. But this doesn't seem
consistent with the way "gem install works".

How difficult is it to implement a simple gem server?
</pre>
</blockquote>
<pre wrap="">
$ gem_server
On the command line. This serves you rdoc documentation and it can
act as a local gem repository server. I've never set up the local
repo so perhaps someone else can chime in./ But it already has
features to do exactly what you want.

</pre>
</blockquote>
<pre wrap="">I will give that a try, but it seems like it is meant to serve your
installed gems. If someone wanted to host and variety of gems (different
versions of gems -- stable, bleeding edge, etc.), I don't think
"gem_server" is the answer. Any ideas what is? Or am I understanding
this incorrectly.

</pre>
</blockquote>
<pre wrap="">
Hi. gem_server can definitely do what you want. You can serve gems
from an alternate directory (with the -d param) if you want to include
a lot of bleeding edge gems that you don't want "installed" on the
host system. Also, if you look in the rubygems distribution under the
"bin" directory, you'll find generate_yaml_index.rb, which you can
use to create a static yaml file that you could serve with your web
server of choice. So you'd have:

<a class="moz-txt-link-freetext" href="http://yourserver.whatever.org/yaml">http://yourserver.whatever.org/yaml</a>
and
<a class="moz-txt-link-freetext" href="http://youserver.whatever.org/gems/mygems.gem">http://youserver.whatever.org/gems/mygems.gem</a>

If you have that structure available, you can serve gems from a
normal web server.

</pre>
</blockquote>
Thanks for the information. I will give it a try.<br>
</body>
</html>

Gems installed but path is wrong	0	Aug 5, 2013
Gems installed to $HOME not recognized	2	Apr 2, 2010
[ANN] rubygems-update 1.6.0 Released	5	Mar 2, 2011
using gems installed via 'sudo gem install'	14	Jan 21, 2011
Install/Update scripts in ruby gems	0	Jan 27, 2010
Can't install gems (Windows)	24	Jan 17, 2010
Rubygems update breaks other gems?	1	Mar 27, 2010
RubyGems question: install vs. update	7	Apr 29, 2009

Update installed gems

Dale Martenson

Ezra Zygmuntowicz

Dale Martenson

Chad Fowler

Dale Martenson

Ask a Question

Similar Threads

Members online

Forum statistics

Latest Threads