Date: Mon, 30 Aug 2010 17:08:51 +0100 From: Eric <freebsdlists-ruby@chillibear.com> To: <ruby@FreeBSD.org> Subject: Re: Current problem reports assigned to ruby@FreeBSD.org Message-ID: <C8A19623.1A2C6%freebsdlists-ruby@chillibear.com> In-Reply-To: <201008301108.o7UB8XBo088818@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C8A19623.1A2C6%freebsdlists-ruby>