From owner-freebsd-ruby@FreeBSD.ORG Mon Apr 13 13:02:27 2015 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8141AAD9 for ; Mon, 13 Apr 2015 13:02:27 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 673E1754 for ; Mon, 13 Apr 2015 13:02:27 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t3DD2RaG055189 for ; Mon, 13 Apr 2015 13:02:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 199141] lang/ruby22: [PATCH][feature request] completely cleanup of gem functions Date: Mon, 13 Apr 2015 13:02:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: swills@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ruby@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2015 13:02:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199141 Steve Wills changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress --- Comment #3 from Steve Wills --- (In reply to ksmakoto from comment #2) Thanks for the testing. I've been testing too and found that it breaks a number of ports. Some, such as devel/rubygem-glib2 and devel/rubygem-gio2 just need to have: require "rubygems" added in certain places. Others, such as databases/ruby-bdb break because they call rdoc and rdoc requires gem. I can patch out the requirement of gem in rdoc, but I can't be sure it will work properly. Upstream, ruby, rdoc and gem are all distributed together and it makes sense for them to depend on each other. So I'm a bit hesitant to go changing things too much. This all makes me unsure that removing the gem bits from ruby is the right thing to do. Can you explain in more detail the original issues that you encountered? What is the trouble you have when gem is included with ruby? (Not saying it's not real, just want to understand all sides of the issue before making a decision which way to go.) -- You are receiving this mail because: You are the assignee for the bug.