From owner-svn-ports-head@FreeBSD.ORG Wed Jul 30 10:47:00 2014 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8BEED706; Wed, 30 Jul 2014 10:47:00 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1CD8A2AB0; Wed, 30 Jul 2014 10:46:59 +0000 (UTC) Received: from [10.6.25.100] ([213.61.170.110]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MU0U9-1X3saO3TfN-00QnIi; Wed, 30 Jul 2014 12:41:37 +0200 Message-ID: <53D8CBDE.6050008@gmx.de> Date: Wed, 30 Jul 2014 12:41:34 +0200 From: olli hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: marino@freebsd.org, Mathieu Arnold , Max Brazhnikov , Alexey Dokuchaev Subject: Re: svn commit: r363361 - in head/editors/fte: . files References: <201407291646.s6TGkjHH090335@svn.freebsd.org> <41D25BC1-AC62-4280-A342-8A2BDD84B1E0@adamw.org> <20140730070412.GA97692@FreeBSD.org> <3898057.T8DsoXnEEp@mercury.ph.man.ac.uk> <53D89EBF.4080805@marino.st> <2D24420529C9ECAEABB9A791@atuin.in.mat.cc> <53D8A2BB.7090704@marino.st> In-Reply-To: <53D8A2BB.7090704@marino.st> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:Sz0cUPmlWD7U9l18B/FiBAyQHFPUm5OQ6P/QqB7Pahh57jQuifY 24Px/BvTl5nD9MBdeQIMI+ST1WZJWmT5dc1si2lzL7nt3EQhfL0jFf4sGJpOGulPDSeFLQc kC57sD9pHiHHrUPI/xw3T6KcHH7u0V/RG8D8sXEJK7WzA4CPwAIKGwySyEE5TtcTNH45TVi vX/aYryZRlysgKxmhPMpQ== Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org, William Grzybowski , Adam Weinberger X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.18 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, 30 Jul 2014 10:47:00 -0000 On 2014-07-30 09:46, John Marino wrote: > On 7/30/2014 09:37, Mathieu Arnold wrote: >> +--On 30 juillet 2014 09:29:03 +0200 John Marino >> wrote: >> | On 7/30/2014 09:25, Max Brazhnikov wrote: >> |> On Wed, 30 Jul 2014 07:04:13 +0000 Alexey Dokuchaev wrote: >> |>> On Tue, Jul 29, 2014 at 01:10:45PM -0400, Adam Weinberger wrote: >> |>>> I'm about to rename all patches that contain ::. Can we please stop >> |>>> producing patches with :: as a path separator, and use __ instead? >> |>> >> |>> Can we also stop using double underscore as it makes patch names so ugly >> |>> and unreadable that I have to spend twice as much time working on ports >> |>> that uses this stupid convention? >> |> >> |> It comes from the makepatch target. >> | >> | Makepatch name convention is no good. I was complaining about this (to >> | bapt) about the lack of a patch name convention and he said to propose >> | one. I've been meaning to do just that, but it also means fixing tools >> | like this. >> >> makepatch name convention is the convention, I find it pretty simple, and >> easy to remember, it does "s|/|__|" and that's all. Whatever the >> convention, there's always someone who will not like it, but it doesn't >> really matter, it's a convention so that everyone knows how to name patch >> files the same way. > > I disagree, there is no convention. Whoever created makepatch attempted > to create a defacto convention that most people don't like (as evidence > that patches not created by makepatch don't use it but rather the more > conventional* single underscore. I don't automatically recognize the > author of makepatch the authority. > > * As seen in other repos such as pkgsrc > > Take a vote. I'd bet the majority of people do not like "__" not just > "someone". I like the `make makepatch' convention, it is simple and you can get the path directly from the patch name without less/cat ... Using the `make makepatch* command has also the charm every patch follows at last a simple rule and you don't have to fiddle around with manual renaming, everyone is able to produce the same patch. About pkgsrc, I really don't care because the discussion is about FreeBSD standards that others can easily adopt and with `make makepatch' a simple standard and tool was added years ago. So I welcome the work that was done recently by adjusting the patch file name. -- olli