From owner-freebsd-ruby@FreeBSD.ORG Thu Nov 15 23:59:42 2012 Return-Path: Delivered-To: freebsd-ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 22EB2C96 for ; Thu, 15 Nov 2012 23:59:42 +0000 (UTC) (envelope-from stas@freebsd.org) Received: from mx0.deglitch.com (cl-414.sto-01.se.sixxs.net [IPv6:2001:16d8:ff00:19d::2]) by mx1.freebsd.org (Postfix) with ESMTP id C37FD8FC12 for ; Thu, 15 Nov 2012 23:59:41 +0000 (UTC) Received: from ssedov-ml.corp.qc (unknown [72.5.114.2]) by mx0.deglitch.com (Postfix) with ESMTPSA id 331588FC2B; Fri, 16 Nov 2012 03:59:31 +0400 (MSK) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: More problems than I care to think about From: Stanislav Sedov In-Reply-To: <76BB3E3F07A4F68477B30C11@utd71538.campus.ad.utdallas.edu> Date: Thu, 15 Nov 2012 15:59:36 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <138C62E5-F2ED-439F-AFA8-777A48B2A87B@freebsd.org> References: <76BB3E3F07A4F68477B30C11@utd71538.campus.ad.utdallas.edu> To: Paul Schmehl X-Mailer: Apple Mail (2.1499) Cc: FreeBSD Ruby List X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 23:59:42 -0000 On Nov 15, 2012, at 11:03 AM, Paul Schmehl = wrote: > I've been trying to port Snorby to FreeBSD. Emphasis on trying. I = run into problems at every turn, and some seem unresolvable. Snorby = requires ruby 1.9.2 or better. The default version on FreeBSD is 1.8. = Putting RUBY_DEFAULT_VER=3D1.9 in /etc/make.conf breaks some of the = rubygem ports that will only build on 1.8. >=20 > sysutils/rubygem-bundler was giving me fits. I discovered that while = the port version is 1.1.5, the current version, which fixes the problems = I was having, is 1.2.2. I created a port update for that and was going = to submit it, but then I discovered devel/rubygem-eventmachine "blows = up" with a core dump if built with 1.9. >=20 > This is beyond discouraging and has caused me to abandon the project = entirely. >=20 > It seems that we need a massive effort to update ruby and rails and = all gems to the latest versions. Who is responsible for that? How can = we get that done? >=20 All the ruby ports are already at the latest version and we do generally = a very good job to keep them updated (and we backport fixes and patches = regularly). Rubygems a lot more complicated as there're a lot of messy dependencies = between them and a lot of times you cannot just update something because a lot = of other stuff that depend on a particular version will break as a result. = That's why my recommendation always was to try to keep all gems out of the ports tree = unless absolutely necessary. Frankly, it does not make much sense at all to = put gems into ports, as gems, unlike ports, support multiple versions being = installed, and a lot of ruby software depend on that feature. I don't know what kind of problem you're experiencing with event = machine, but I guess it is not ruby related. It'd be helpful if you can post more = info. I use eventmachine both from ports and gems for several production application = with ruby 1.9 and have not seen any segfaults (except the one that was housed = by my own C extension library).=20 -- ST4096-RIPE