From: "Berger, Daniel" Date: 2006-07-12T03:03:26+09:00 Subject: Re: Developmetn Releases on Rubyforge > -----Original Message----- > From: transfire@gmail.com [mailto:transfire@gmail.com] > Sent: Tuesday, July 11, 2006 11:57 AM > To: ruby-talk ML > Subject: Developmetn Releases on Rubyforge > > > Wish there a way to mark a Rubyforge release as "official" so > that a later development releases wouldn't become the default > package/gem. > > What solutions to this do others use? > T. Simple - I don't put out a gems for development releases. You want it? You gotta grab it yourself. :) Does rubygems support a "status" option, i.e. "stable", "alpha", "development", etc? Then set the default to only install "stable" gems, with an option to install the specified status level, e.g. gem install foo --status=any would grab the latest and greatest, regardless of dev status. Might be handy. Regards, Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.