Date: Mon, 13 Apr 2015 13:02:27 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 199141] lang/ruby22: [PATCH][feature request] completely cleanup of gem functions Message-ID: <bug-199141-21402-KN9JhEBOiO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-199141-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-199141-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199141 Steve Wills <swills@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress --- Comment #3 from Steve Wills <swills@FreeBSD.org> --- (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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199141-21402-KN9JhEBOiO>