From owner-svn-ports-head@freebsd.org Wed Mar 13 17:17:23 2019 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0439A153A7F5 for ; Wed, 13 Mar 2019 17:17:23 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D9418ABD5; Wed, 13 Mar 2019 17:17:22 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by fc.opsec.eu with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1h47VH-0006ni-VV; Wed, 13 Mar 2019 18:17:19 +0100 Date: Wed, 13 Mar 2019 18:17:19 +0100 From: Kurt Jaeger To: Alexey Dokuchaev Cc: Kurt Jaeger , ports-committers@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r495383 - in head/java: . wildfly16 wildfly16/files Message-ID: <20190313171719.GS88817@fc.opsec.eu> References: <201903111943.x2BJhchV074502@repo.freebsd.org> <20190312021938.GA4479@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190312021938.GA4479@FreeBSD.org> X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2019 17:17:23 -0000 Hi! > > Log: > > New port: java/wildfly16 [...] > Its name suggests it should've been repocopied from one of the earlier > versions but it was not, why is that? I missed it, that is common for arkane rules. Now, would some person who knows why we do keep to certain rites add one section to https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ports.html#ports-qa-repocopies to explain *why* we do this ? We already have a 'when' and 'how', but no 'why' section. A section to explain how a repo-copy can be re-applied after it was done wrong, would probably help others as well. As can be seen by my recent attempt, it's not simple. Any chance to have a script similar to the mfh-script, that re-does repo-copies ? -- pi@FreeBSD.org +49 171 3101372 One year to go !