Date: Wed, 13 Mar 2019 18:17:19 +0100 From: Kurt Jaeger <pi@freebsd.org> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: Kurt Jaeger <pi@freebsd.org>, 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> In-Reply-To: <20190312021938.GA4479@FreeBSD.org> References: <201903111943.x2BJhchV074502@repo.freebsd.org> <20190312021938.GA4479@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190313171719.GS88817>