From owner-freebsd-ruby@freebsd.org Sat Dec 21 21:57:07 2019 Return-Path: Delivered-To: freebsd-ruby@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C9ECA1DDA2E for ; Sat, 21 Dec 2019 21:57:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 47gKGC534Gz4gD8 for ; Sat, 21 Dec 2019 21:57:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id AD41F1DDA2D; Sat, 21 Dec 2019 21:57:07 +0000 (UTC) Delivered-To: ruby@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AD0701DDA2C for ; Sat, 21 Dec 2019 21:57:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47gKGC4Bmxz4gD6 for ; Sat, 21 Dec 2019 21:57:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 719191DA85 for ; Sat, 21 Dec 2019 21:57:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id xBLLv7q7067378 for ; Sat, 21 Dec 2019 21:57:07 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xBLLv7hu067377 for ruby@FreeBSD.org; Sat, 21 Dec 2019 21:57:07 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 237833] lang/ruby26: irb, rdoc, ri is broken Date: Sat, 21 Dec 2019 21:57:07 +0000 X-Bugzilla-Reason: CC 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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: yasu@utahime.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: meta@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.29 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Dec 2019 21:57:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237833 --- Comment #18 from Yasuhiro KIMURA --- (In reply to Koichiro Iwao from comment #16) Iwao-san, Sorry for late response. I tried removing this patch and saw what happened.= The result was that following gems were installed under /usr/local/lib/ruby/2.6 (directory where rubygem ports install their files). * bundler 1.17.2 * did_you_mean 1.3.0 * irb 1.0.0 * minitest 5.11.3 * net-telnet 0.2.0 * power_assert 1.1.3 * rake 12.3.2 * rdoc 6.1.2 * test-unit 3.2.9 * xmlrpc 0.3.0 I found some of them exists as rubygem port in ports tree. And some of such ports has same version as above. That is, removing this patch results in installed file conflict with some rubygem ports. So this patch shouldn't be removed. I also found there isn't port of did_you_mean gem in ports tree. S= o it may be we should create it. >From this result I think we need to review other patches and understand what they do and/or why they are necessary. Furthermore, it may be we need to ask ourselves following fundamental quest= ion. "What should (or shouldn't) be install by this port?" To be honest, I think I should have made consensus about answer to this question with others before I start creating lang/ruby26 port. --=20 You are receiving this mail because: You are on the CC list for the bug.=