From owner-freebsd-ruby@FreeBSD.ORG Wed Mar 16 11:25:57 2011 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70BE81065672 for ; Wed, 16 Mar 2011 11:25:57 +0000 (UTC) (envelope-from freebsdlists-ruby@chillibear.com) Received: from mail.sundive.org (mail.sundive.org [212.13.197.214]) by mx1.freebsd.org (Postfix) with ESMTP id 325C48FC1A for ; Wed, 16 Mar 2011 11:25:56 +0000 (UTC) Received: from 179.218.125.91.gr7.adsl.brightview.com ([91.125.218.179] helo=[192.168.0.44]) by sundive.org with esmtpsa (TLSv1:DES-CBC3-SHA:168) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1Pzosr-000MNv-KQ; Wed, 16 Mar 2011 11:27:24 +0000 User-Agent: Microsoft-Entourage/12.28.0.101117 Date: Wed, 16 Mar 2011 11:25:42 +0000 From: Eric To: Message-ID: Thread-Topic: making Ruby 1.9 default Thread-Index: AcvjzOJRCwTH58gV0UyJ4QgEcVnuYg== In-Reply-To: <1300272269.1973.16.camel@localhost> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam_score: -2.2 X-Spam_score_int: -21 X-Spam_bar: -- X-Spam: No X-bounce-key: sundive.org-1; freebsdlists-ruby@chillibear.com; 1300274845; d39d8937; Cc: Subject: Re: making Ruby 1.9 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: Wed, 16 Mar 2011 11:25:57 -0000 > From: paranormal [SNIP] > This is good idea. But beautiful port portupgrade :), > not work with 1.9 version. What about ports/144605 - "[PATCH] Get ports-mgmt/portupgrade to build under Ruby 1.9.1" I've not tried it, but does that patch do what it says on the tin? > I'm ruby programmer and use tags like so: > > .if ${.CURDIR:M*/*/rubygem-*} > RUBY_DEFAULT_VER=1.9 > .endif > > .if ${.CURDIR:M*/*/ruby-*} > RUBY_DEFAULT_VER=1.9 > .endif > > > I think we need update portupgrade before update system ruby. There are plenty of outstanding PRs regarding portupgrade, which does seem to suffer from being both loved and unloved (in terms of maintenance). I personally use it, but am wondering if it's time to switch to Doug's PortMaster now... However given that portupgrade is often noted in documentation as almost the default tool for doing upgrades of ports then it does seem sensible that we should all try our best to fix it. I personally think we should still aim to get to the default of 1.9 and aiming for the 9.0 release seems a sensible target to go for, if part of that process would seem to be getting portupgrade sorted then so be it. Regards Eric