From owner-svn-ports-all@freebsd.org Wed Jan 27 08:58:25 2016 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9453A6FD91; Wed, 27 Jan 2016 08:58:25 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B73861D56; Wed, 27 Jan 2016 08:58:25 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [192.168.1.21] (248.Red-83-39-200.dynamicIP.rima-tde.net [83.39.200.248]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id F31B443BB9; Wed, 27 Jan 2016 02:58:22 -0600 (CST) Subject: Re: svn commit: r407270 - head/ports-mgmt/portmaster To: koobs@FreeBSD.org, Alexey Dokuchaev References: <201601261123.u0QBNcvL091258@repo.freebsd.org> <56A86CAD.7030507@marino.st> <56A8747E.5080703@FreeBSD.org> <20160127081700.GA20812@FreeBSD.org> <56A87FCE.6080305@FreeBSD.org> <20160127084230.GA28230@FreeBSD.org> <56A88489.5020507@FreeBSD.org> Cc: Martin Wilke , ports-committers@freebsd.org, "svn-ports-all@FreeBSD.org" , "svn-ports-head@FreeBSD.org" Reply-To: marino@freebsd.org From: John Marino Message-ID: <56A886AD.4070301@marino.st> Date: Wed, 27 Jan 2016 09:58:21 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56A88489.5020507@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2016 08:58:25 -0000 On 1/27/2016 9:49 AM, Kubilay Kocak wrote: > On 27/01/2016 7:42 PM, Alexey Dokuchaev wrote: >> On Wed, Jan 27, 2016 at 07:29:02PM +1100, Kubilay Kocak wrote: >>> On 27/01/2016 7:17 PM, Alexey Dokuchaev wrote: >>>> On Wed, Jan 27, 2016 at 06:40:46PM +1100, Kubilay Kocak wrote: >>>>> Given what the term 'deprecated' implies, I would use a pre-everything: >>>>> message instead. >>>> >>>> That's a good idea actually. >>> >>> It would be nice to have something framework'ey that is less loaded than >>> DEPRECATED, but more specific and consistent than your standard ECHO_MSG >>> or pkg-message. Like CAUTION/ALERT/WARNING/INFORMATIONAL or similar. >> >> Personally I don't think that DEPRECATED is *that* loaded. IMHO it works >> quite fine for cases like this one, and no, it should not imply expiration >> date. But perhaps there is warrant for CAUTION/ALERT/WARNING/INFORMATION >> or similar indeed. > > Neither do I. However, while *we* might grok it's non-specific nature, > but I'll bet you $100 that the vast majority of software users (not just > of FreeBSD) would go by the dictionary definition, or some equivalent > of it: > > 3. Computers: To mark (a component of a software standard) as obsolete > to warn against its use in the future so that it may be phased out. > > DEPRECATED's non specific nature is kind of what I was getting at, and > why I think there's room for something better. > It seems to me that definition is perfect. It *is* obsolete, people should be warned, and yes, eventually it will likely be phased out (assuming nothing changes) What's wrong with that? Until then, keep using it if you want.