From owner-svn-ports-all@FreeBSD.ORG Tue Apr 15 13:16:32 2014 Return-Path: Delivered-To: svn-ports-all@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 EAD635B9; Tue, 15 Apr 2014 13:16:32 +0000 (UTC) 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 85D1918EF; Tue, 15 Apr 2014 13:16:32 +0000 (UTC) Received: from [192.168.0.20] (unknown [130.255.19.191]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 075E843BB3; Tue, 15 Apr 2014 08:16:14 -0500 (CDT) Message-ID: <534D310B.4010303@marino.st> Date: Tue, 15 Apr 2014 15:15:55 +0200 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Bryan Drewery , marino@freebsd.org, Baptiste Daroussin , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r351326 - head/Mk References: <201404151249.s3FCnkvQ026905@svn.freebsd.org> <534D2D57.60001@FreeBSD.org> <534D2F2B.4030606@marino.st> <534D3055.3070406@FreeBSD.org> In-Reply-To: <534D3055.3070406@FreeBSD.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: marino@freebsd.org List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2014 13:16:33 -0000 On 4/15/2014 15:12, Bryan Drewery wrote: > What I'd like to do is have the build gather all deprecated information > and put it into the repo metadata. Then a 'pkg update' will get the new > deprecation information for that repository. Then the dates can be > displayed at pkg upgrade and in periodic scripts. All I care about is the end result. If you know a better way to implement that, I'm all for it. Displaying as part of pkg update will be good as long as it shows at the end (rather than scrolling off or otherwise hard to see). John