From owner-svn-ports-head@freebsd.org Thu Mar 14 17:53:51 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 0DDEB15261D3 for ; Thu, 14 Mar 2019 17:53:51 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B47C8AF8F; Thu, 14 Mar 2019 17:53:50 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 7CA34524E; Thu, 14 Mar 2019 17:53:50 +0000 (UTC) Date: Thu, 14 Mar 2019 17:53:50 +0000 From: Alexey Dokuchaev To: Torsten Zuehlsdorff 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: <20190314175350.GA94077@FreeBSD.org> References: <201903111943.x2BJhchV074502@repo.freebsd.org> <20190312021938.GA4479@FreeBSD.org> <20190313171719.GS88817@fc.opsec.eu> <20190314161923.GA5046@FreeBSD.org> <88a46b08-1691-a312-8b7d-aa5a0617cd3d@toco-domains.de> <20190314163824.GA32373@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190314163824.GA32373@FreeBSD.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 9B47C8AF8F X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.87 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.87)[-0.873,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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: Thu, 14 Mar 2019 17:53:51 -0000 On Thu, Mar 14, 2019 at 04:38:24PM +0000, Alexey Dokuchaev wrote: > On Thu, Mar 14, 2019 at 05:29:40PM +0100, Torsten Zuehlsdorff wrote: > > On 14.03.19 17:19, Alexey Dokuchaev wrote: > > > On Wed, Mar 13, 2019 at 06:17:19PM +0100, Kurt Jaeger wrote: > > >>>> 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. > > > > > > There's nothing arcane about repocopies Kurt. I'm honestly surprised > > > why people make this mistake again and again. When you resurrect a > > > port you make a repocopy. When you spin-off a new branch based on a > > > previous version you make a repocopy [...] > > > > > > Upstream renames their software, you make a repocopy, etc. > > > > A rename should be a "svn mv" instead of "svn cp"? Or am i mistaken? > > Well yeah, I didn't go to the very details. However, svn move is > equivalent to an svn copy followed by svn delete. To make myself 100% clear: repocopy != always "svn cp", it's about copying of the previous history. Naturally, for software renames, or when a port is moved from one category to another, one would usually use "svn mv" (which still implies "svn cp" under the hood). ./danfe