X-BeenThere: rubyonrails-core@googlegroups.com
Received: by 10.101.143.28 with SMTP id v28ls1666365ann.0.p; Mon, 22 Feb 2010 
	03:08:06 -0800 (PST)
Received: by 10.101.3.19 with SMTP id f19mr8264530ani.9.1266836885983;
        Mon, 22 Feb 2010 03:08:05 -0800 (PST)
Received: by 10.101.3.19 with SMTP id f19mr8264529ani.9.1266836885934;
        Mon, 22 Feb 2010 03:08:05 -0800 (PST)
Return-Path: <hon...@phusion.nl>
Received: from mail-yx0-f163.google.com (mail-yx0-f163.google.com [209.85.210.163])
        by gmr-mx.google.com with ESMTP id 18si229169ywh.5.2010.02.22.03.08.05;
        Mon, 22 Feb 2010 03:08:05 -0800 (PST)
Received-SPF: pass (google.com: domain of hon...@phusion.nl designates 209.85.210.163 as permitted sender) client-ip=209.85.210.163;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of hon...@phusion.nl designates 209.85.210.163 as permitted sender) smtp.mail=hon...@phusion.nl
Received: by yxe35 with SMTP id 35so13134497yxe.2
        for <rubyonrails-core@googlegroups.com>; Mon, 22 Feb 2010 03:08:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.201.3 with SMTP id y3mr215848anf.43.1266836885501; Mon, 22 
	Feb 2010 03:08:05 -0800 (PST)
Date: Mon, 22 Feb 2010 03:08:05 -0800 (PST)
In-Reply-To: <245fb4701002220225t1e5a92f7v716343379ef89e85@mail.gmail.com>
X-IP: 77.250.47.10
References: <71996df7-9d3a-4d9b-a7a6-8642cb0da401@q16g2000yqq.googlegroups.com> 
	<245fb4701002220225t1e5a92f7v716343379ef89e85@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; 
	rv:1.9.2) Gecko/20100115 Firefox/3.6,gzip(gfe),gzip(gfe)
Message-ID: <a28ea740-d996-40a7-acae-cf853b15af53@g11g2000yqe.googlegroups.com>
Subject: Re: Having Rails 2.3pre or Rack 1.1 installed breaks Rails 2.x
From: Hongli Lai <hon...@phusion.nl>
To: "Ruby on Rails: Core" <rubyonrails-core@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Feb 22, 11:25=A0am, Yehuda Katz <wyc...@gmail.com> wrote:
> Hongli,
>
> This is a classic problem of the sort Bundler was created to solve. The o=
nly
> possible solutions are to either ensure that these versions of the gems d=
o
> not coexist in a system gems repo or to use a tool like bundler to
> pre-resolve the list of needed dependencies.
>
> Simply changing the 2.3 dependency to >=3D 1.0.0 is a problem because Rai=
ls
> could potentially break if a new (incompatible) version of Rack is releas=
ed.
> The entire purpose of the ~> dependency is to say "I know for sure I work=
 on
> Rack 1.0.x, but not some future version".

Yeah but having all the system gems become unusable is not a good
thing. It's good that Bundler prevents problems but I'd rather see
these sorts of problems not occurring in the first place so that
Bundler is not needed so often.

As for Rack breakage, wouldn't that be easily solved with some version
numbering discipline? If Rack decides to break an interface then it
should bump its major version to 2.