From nobody Thu Dec 23 16:34:24 2021 X-Original-To: dev-commits-ports-main@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 673F818F445D; Thu, 23 Dec 2021 16:34:30 +0000 (UTC) (envelope-from meta@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JKbPf0yWHz3R5n; Thu, 23 Dec 2021 16:34:30 +0000 (UTC) (envelope-from meta@FreeBSD.org) Received: from icepick.vmeta.jp (unknown [IPv6:2405:6586:2280:1200:18ce:703:69c5:c079]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: meta/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 71A87E4A2; Thu, 23 Dec 2021 16:34:28 +0000 (UTC) (envelope-from meta@FreeBSD.org) Date: Fri, 24 Dec 2021 01:34:24 +0900 From: Koichiro Iwao To: Yasuhiro Kimura Cc: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org Subject: Re: git: a784d1e5dcb6 - main - devel/rubygem-rdoc: Update to 6.3.3 Message-ID: <20211223163424.fq35dzowhachqwnh@icepick.vmeta.jp> X-Operating-System: FreeBSD 13.0-STABLE amd64 References: <202112030756.1B37uSCq022554@gitrepo.freebsd.org> <20211223023014.sw2it535yxmfyijc@icepick.vmeta.jp> <20211223.163818.2197196243075257637.yasu@FreeBSD.org> List-Id: Commits to the main branch of the FreeBSD ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-main@freebsd.org X-BeenThere: dev-commits-ports-main@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20211223.163818.2197196243075257637.yasu@FreeBSD.org> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1640277270; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4ojhEotEDPsvK1jciCPEfRUATcbTeqfkRWsy263RTko=; b=PbwD660jveUQABoNdqP7AVWYAg/kUxQlGfDBDRjyk7TNhL7y0CpF1v2kVdkyVmN6+bOYI3 2YWaODQYPhdupWDlCOhLAdSi2np1oG52caNCfzAq6d6ItBW4l3Uuf1+O/EzjdUX00QCX9v Bo942vaIQtkUEkjWPALnGW78l7n8ZzP0/97631CQ5GVqCDVWTPDUAvIAdoZygBZrLIzSSz KQ680T7wfwsyVQ1xBU0EosHcW4rxdkfqmgv63neeeksLY84LEOzOmMCtt6h5DaDpPJjHPp ki2JVZ2KYbLyyMMDNIAeT8uyBER1hWPQ0kVy2YX9lHM6nWyrwKG2sn/P9iTspA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1640277270; a=rsa-sha256; cv=none; b=w7PMB1bRKmEB8g1lUBTTchnEGt5eUpkHGJwQPJ9ml+C8gf7FeABbp/LdMS7tZo49xUWdVW JrrI3oHkeYC9naUazKDEKX8c20tj3RkwEMKmhk/e9XHH6YWUyGd7obBo/hge4GVQsN3GD9 o9w0oXWW05mtbsHzw6P2rzx/fswUUkd1AaPHvB1ZBUbbJNRlwuPV1q3dkAxIDB9HNWQIh0 VOV72hrMvoPDOn+F9d+Rl1xHdCGg3RqswZNECoLF0wlO221118lp/mt4fAearHiqGw42cF aWDNDKutO5L+8iTgLv75LDYTvE8se6BfAxTYigMh7Ir1TbP6Zk7EFMQVgZ6/7Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Thu, Dec 23, 2021 at 04:38:18PM +0900, Yasuhiro Kimura wrote: > > It is my understanding that it requires approval of team's member to > update a port if MAINTAINER of the port is team such as desktop@, > emacs@, perl@, python@, ruby@, x11@, etc. > > Isn't it correct? I don't think it is necessary if the changeset is a simple update of each leaf port because MAINTAINER=ruby@ is also default pool for Ruby related ports. I once grabbed rubygem-irb, ruby-build, and some other ports but returned to ruby@. I intend to make these ports open to FreeBSD Ruby folks. Generally, it is nice to get member's approval before making changes. When you're making big changes such as Ruby framework refinements, you must get member's or portmgr's approval. If you're unsure of something and you want to get your changes reviewed, it is better to request it explicitly. -- meta