From owner-freebsd-ruby@FreeBSD.ORG  Mon Aug 30 16:09:05 2010
Return-Path: <owner-freebsd-ruby@FreeBSD.ORG>
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 1A4C210656A6
	for <ruby@FreeBSD.org>; Mon, 30 Aug 2010 16:09:05 +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 CF8808FC1E
	for <ruby@FreeBSD.org>; Mon, 30 Aug 2010 16:09:04 +0000 (UTC)
Received: from 87.114.196.227.homesurf.thn-ag3.dyn.plus.net ([87.114.196.227]
	helo=[192.168.0.44])
	by sundive.org with esmtpsa (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.71 (FreeBSD))
	(envelope-from <freebsdlists-ruby@chillibear.com>)
	id 1Oq6wq-0002NE-CE
	for ruby@FreeBSD.org; Mon, 30 Aug 2010 17:11:09 +0100
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Mon, 30 Aug 2010 17:08:51 +0100
From: Eric <freebsdlists-ruby@chillibear.com>
To: <ruby@FreeBSD.org>
Message-ID: <C8A19623.1A2C6%freebsdlists-ruby@chillibear.com>
Thread-Topic: Current problem reports assigned to ruby@FreeBSD.org
Thread-Index: ActIXaLCVUe8bq0X8kqsOTeM7SUCvA==
In-Reply-To: <201008301108.o7UB8XBo088818@freefall.freebsd.org>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-SA-Exim-Connect-IP: 87.114.196.227
X-SA-Exim-Mail-From: freebsdlists-ruby@chillibear.com
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sun.sundive.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED,BAYES_00,
	TVD_RCVD_IP autolearn=ham version=3.3.1
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on sundive.org)
X-bounce-key: sundive.org-1; freebsdlists-ruby@chillibear.com; 1283184671;
	8f9aca5a; 
Cc: 
Subject: Re: Current problem reports assigned to ruby@FreeBSD.org
X-BeenThere: freebsd-ruby@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: FreeBSD-specific Ruby discussions <freebsd-ruby.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ruby>
List-Post: <mailto:freebsd-ruby@freebsd.org>
List-Help: <mailto:freebsd-ruby-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Aug 2010 16:09:05 -0000

Hi all,

I was just reading through ports/147809, which in summary is about a broken
install of databases/ruby-dbi.  That break came about because a gem it
depended on (devel/rubygem-deprecated) was upgraded and the interface in the
gem changed between versions.

So I was wondering what our approach was in situations like this where (in
this case) one library depends on a particular version of a gem not >= or
anything.  On my Mac where gems are just installed using the gem commands
directly I end up with numerous versions installed because I rarely remove
an earlier version so I never really encounter this problem, but with ports
on FreeBSD we remove and replace the gem with the latest.

The easiest is probably to have another port for particular cases like this
and just list that in the DEPENDS.  So in this case create a
devel/rubygem-deprecated-2_0_1.

Anyone got any neater ideas?  Perhaps there are not enough to worry about a
neater solution, but I thought it was worth a quick ponder before I try/test
and submit a some patches to hopefully fix ports/147809.

Cheers

Eric