Date: Tue, 15 Apr 2014 08:50:09 -0500 From: Bryan Drewery <bdrewery@FreeBSD.org> To: marino@freebsd.org Cc: svn-ports-head@freebsd.org, Baptiste Daroussin <bapt@freebsd.org>, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r351326 - head/Mk Message-ID: <235932fa945a702e78ca04f197fbc739@shatow.net> In-Reply-To: <534D310B.4010303@marino.st> References: <201404151249.s3FCnkvQ026905@svn.freebsd.org> <534D2D57.60001@FreeBSD.org> <534D2F2B.4030606@marino.st> <534D3055.3070406@FreeBSD.org> <534D310B.4010303@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2014-04-15 08:15, John Marino wrote: > 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 I'm planning a periodic script too. I agree on the scrolling concern. It also occurred to me that we're planning to deprecate 4500 ports soon due to not being staged (need to announce the timeline for this still.) Some of these ports don't even build, and this problem exists outside of this situation too. So requiring a port rebuild to notify user won't work if it doesn't build! -- Regards, Bryan Drewery
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?235932fa945a702e78ca04f197fbc739>