From owner-freebsd-ruby@FreeBSD.ORG Tue Jun 5 00:25:09 2012 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E2C5C1065674; Tue, 5 Jun 2012 00:25:09 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b2]) by mx1.freebsd.org (Postfix) with ESMTP id A06E78FC12; Tue, 5 Jun 2012 00:25:09 +0000 (UTC) Received: from meatwad.mouf.net (cpe-024-162-230-236.nc.res.rr.com [24.162.230.236]) (authenticated bits=0) by mouf.net (8.14.4/8.14.4) with ESMTP id q550P82U055955 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 4 Jun 2012 20:25:08 -0400 (EDT) (envelope-from swills@FreeBSD.org) Message-ID: <4FCD51E4.4030309@FreeBSD.org> Date: Mon, 04 Jun 2012 20:25:08 -0400 From: Steve Wills User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120528 Thunderbird/12.0.1 MIME-Version: 1.0 To: Stanislav Sedov References: <4FC96D45.8080904@FreeBSD.org> <20120601193059.af9201da.stas@FreeBSD.org> In-Reply-To: <20120601193059.af9201da.stas@FreeBSD.org> X-Enigmail-Version: 1.5pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mouf.net [204.109.58.86]); Mon, 04 Jun 2012 20:25:09 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.97.2 at mouf.net X-Virus-Status: Clean Cc: ports@FreeBSD.org, ruby@FreeBSD.org Subject: Re: Ruby 1.9 as default X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 00:25:10 -0000 On 06/01/12 22:30, Stanislav Sedov wrote: > > I'm not sure it's a good idea. > Ruby 1.9 still has some nasty bugs on FreeBSD, related to the threads and > fork. That is fork in ruby 1.9 hangs sometimes... The ONLY thing I can find is this: http://bugs.ruby-lang.org/issues/2097 which implies that it's fixed. If there's more to this issue than "broken on 7.3 and earlier", PLEASE let me know. Steve