From owner-freebsd-ruby@FreeBSD.ORG Mon Aug 30 20:49:24 2010 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 924BD10656B6 for ; Mon, 30 Aug 2010 20:49:24 +0000 (UTC) (envelope-from pgollucci@p6m7g8.com) Received: from cell.p6m7g8.net (static-71-178-236-107.washdc.fios.verizon.net [71.178.236.107]) by mx1.freebsd.org (Postfix) with ESMTP id 2E66F8FC16 for ; Mon, 30 Aug 2010 20:49:23 +0000 (UTC) Received: from philip.hq.rws (wsip-174-79-184-239.dc.dc.cox.net [174.79.184.239]) (authenticated bits=0) by cell.p6m7g8.net (8.14.4/8.14.3) with ESMTP id o7UKn8Ip020198 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO); Mon, 30 Aug 2010 20:49:08 GMT (envelope-from pgollucci@p6m7g8.com) Message-ID: <4C7C1944.9070400@p6m7g8.com> Date: Mon, 30 Aug 2010 20:49:08 +0000 From: "Philip M. Gollucci" Organization: P6M7G8 Inc. User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.9) Gecko/20100607 Thunderbird/3.0.4 MIME-Version: 1.0 To: Eric References: In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on cell.p6m7g8.net Cc: ruby@freebsd.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2010 20:49:24 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/30/10 16:08, Eric wrote: > 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. Yes, that is a solution, and one I've pondered for a while. Since this is few and far between its usually easier to pester the upstream maintainer to fix their gem for the api changes. It could also be the case that the gem say ~> but really >= will work for minor changes. In that case I've re-rolled a local .gem file and hosted it in my ~. Eventually things catch up. - ------------------------------------------------------------------------ 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollucci@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer, FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iD8DBQFMfBlEdbiP+9ubjBwRAjJ5AJ9Cdfk1PAZTn1hO9AOQB8OSWafESACeO5GF Y7L+iLHYXa/UVTP1YSXbGwc= =nLZc -----END PGP SIGNATURE-----