Date: Tue, 12 Mar 2002 19:44:13 -0600 From: David Syphers <dsyphers@uchicago.edu> To: batz <batsy@vapour.net> Cc: freebsd-security@FreeBSD.ORG Subject: Re: Managing port security upgrades (was:Re: PHP 4.1.2) Message-ID: <200203130144.g2D1iDn21277@midway.uchicago.edu> In-Reply-To: <Pine.BSF.4.21.0203121730170.5001-100000@vapour.net> References: <Pine.BSF.4.21.0203121730170.5001-100000@vapour.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 12 March 2002 04:55 pm, batz wrote: > Back to my original post, about whether cvs would be a useful way to > manage security specific information, so that people who just wanted to > fix open vulnerabilities could do so in a way that did not involve > sucking down most of the ports tree if they had not upgraded it in a while. But if you just cvsup'd the vulnerable ports and you hadn't cvsup'd the rest in a while, there's a good chance some of them wouldn't build due to dependency issues. -David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203130144.g2D1iDn21277>