From owner-freebsd-questions@FreeBSD.ORG Fri Aug 25 16:06:18 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9571F16A4DD for ; Fri, 25 Aug 2006 16:06:18 +0000 (UTC) (envelope-from freebsd@philip.pjkh.com) Received: from bravo.pjkh.com (bravo.pjkh.com [72.36.232.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35E6543D55 for ; Fri, 25 Aug 2006 16:06:17 +0000 (GMT) (envelope-from freebsd@philip.pjkh.com) Received: from bravo.pjkh.com (bravo.pjkh.com [72.36.232.219]) by bravo.pjkh.com (Postfix) with ESMTP id E59D613C892; Fri, 25 Aug 2006 11:12:02 -0500 (CDT) Received: by bravo.pjkh.com (Postfix, from userid 1000) id 5FB5113C8AA; Fri, 25 Aug 2006 11:12:02 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by bravo.pjkh.com (Postfix) with ESMTP id 5E63913C8A2; Fri, 25 Aug 2006 11:12:02 -0500 (CDT) Date: Fri, 25 Aug 2006 11:12:02 -0500 (CDT) From: Philip Hallstrom To: Ashley Moran In-Reply-To: <200608251654.39833.work@ashleymoran.me.uk> Message-ID: <20060825111028.E66544@bravo.pjkh.com> References: <200608251654.39833.work@ashleymoran.me.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-questions@freebsd.org Subject: Re: rubygems in ports X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Aug 2006 16:06:18 -0000 > I've been meaning to ask this for a while... what is the motivation for > including individual Ruby gems in ports? It strikes me as unnecessary > duplication, as the gem tool works well on its own, even for gems with C > code. Are there many gems with FreeBSD-specific extensions or dependencies? > > And which is preferable - pure gems or ports+gems? I was just wondering the same thing. I don't think it hurts to have both though... I would assume that the port version has been a little better tested to work with the rest of the ruby world as well as make sure it picks up any c extensions (mysql, gd gems for example that need external libs) automatically... maybe?