Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion One-Click Ruby Installer 184-16 preview2 is available!

Path: g2news1.google.com!news2.google.com!news4.google.com!news2.volia.net!npeer.de.kpn-eurorings.net!noris.net!not-for-mail
From: Jim Weirich <j...@weirichhouse.org>
Newsgroups: comp.lang.ruby
Subject: Re: One-Click Ruby Installer 184-16 preview2 is available!
Date: Thu, 2 Feb 2006 00:59:26 +0900
Lines: 23
Message-ID: <f0118dca42af71d14f056c7d55b12334@ruby-forum.com>
References: <31d15f490601301532o5686dfe9j89d54773027cc80d@mail.gmail.com> <1138684786.16636.47.camel@hal> <3a3d58af0601310653v7b489686j3bf4a6b8fe6d846@mail.gmail.com> <43DFB294.208@path.berkeley.edu>
NNTP-Posting-Host: sinus.lauschmusik.de
Content-Type: text/plain; charset=utf-8
X-Trace: ork-un.noris.net 1138809592 23209 213.95.32.201 (1 Feb 2006 15:59:52 GMT)
X-Complaints-To: news@noris.net
NNTP-Posting-Date: Wed, 1 Feb 2006 15:59:52 +0000 (UTC)
X-received-from: This message has been automatically forwarded from
   the ruby-talk mailing list by a gateway at lauschmusik.de. If it is
   SPAM, it did not originate at lauschmusik.de. Please report the 
   original sender, and not us. Thanks!
   Please see http://hypermetrics.com/rubyhacker/clrFAQ.html#tag24 to.
In-Reply-To: <43DFB294.208@path.berkeley.edu>
X-ML-Name: ruby-talk
X-Mail-Count: 177668
X-ruby-talk: <f0118dca42af71d14f056c7d55b12...@ruby-forum.com>
X-rubymirror: yes

Joel VanderWerf wrote:
> Is there some way to "lock" older gems that are needed by applications?
> Or would FreeRIDE have to be a gem itself and have an explicit 
> dependency?

I assume you mean lock down so that the gem cleanup command won't remove 
particular versions.

There is no direct way to do this in RubyGems.  However, you could 
create a gem of your own that installed no software but did depened on 
the versions of the software you needed.  It is pretty trivial to create 
gems, so this is not hard.  As long as your "lock down" gem is 
installed, the cleanup command won't remove the referenced gem versions. 
(caveat: technique untried, but can't think of a reason it wouldn't 
work).

--
-- Jim Weirich

-- 
Posted via http://www.ruby-forum.com/.