[Rubygems-developers] Gem#status?

Luis Lavena luislavena at gmail.com
Fri Nov 14 18:11:48 EST 2008

On Fri, Nov 14, 2008 at 7:57 PM, Eric Hodel <drbrain at segment7.net> wrote:
> On Nov 14, 2008, at 10:55 AM, Trans wrote:
>> On Nov 13, 3:51 pm, Eric Hodel <drbr... at segment7.net> wrote:
>>> On Nov 13, 2008, at 10:34 AM, Trans wrote:
>>>>> So ~> for 2.1.0 will be the same as 2.1.0.rc30 gem installed in the
>>>>> user system.
>>>> No. I think people use ~> when they expect very tight and rational
>>>> versioning. So ~> means production code only, and rc30 would not fit
>>>> the bill. That's what I meant by "not consider".
>>> ~> 2.1.0 means any version between 2.1.0 and 2.1.9... only.  It
>>> doesn't mean anything else (nor should it).
>>> 2.1.0.rc30 is less than 2.1.0, and 2.1.9... is less than 2.2.0.rc1.
>>> This was described further up the thread.
>> Ok, great. That's exactly what I was saying. But is the extra dot
>> necessary? "2.1.0rc1" and such is common, but an extra dot, I've seen
>> anyone use that notation before.
> It makes things easier in RubyGems.

Cool with that.

>> There's two sides to this. Installing is one of them. What about the
>> constraint on the gem method?
> Don't install prerelease gems if you don't want to use them.  Uninstall
> prerelease gems if they don't work like you want.
> If you're going to a foot shooting party then RubyGems won't restrict you to
> a BB gun.

So that means Kernel::gem or Kernel::require will automatically pick
the RC version unless you explicitly tell them not to?

Irb playing with Gem::Requirement and Gem::Versions looks like...

Luis Lavena
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

More information about the Rubygems-developers mailing list