From owner-freebsd-security Tue Mar 12 17:44:24 2002 Delivered-To: freebsd-security@freebsd.org Received: from midway.uchicago.edu (midway.uchicago.edu [128.135.12.12]) by hub.freebsd.org (Postfix) with ESMTP id 341CF37B420 for ; Tue, 12 Mar 2002 17:44:16 -0800 (PST) Received: from there (adsl-65-42-135-112.dsl.chcgil.ameritech.net [65.42.135.112]) by midway.uchicago.edu (8.11.6/8.11.6) with SMTP id g2D1iDn21277; Tue, 12 Mar 2002 19:44:13 -0600 (CST) Message-Id: <200203130144.g2D1iDn21277@midway.uchicago.edu> Content-Type: text/plain; charset="iso-8859-1" From: David Syphers Reply-To: charon@seektruth.org To: batz Subject: Re: Managing port security upgrades (was:Re: PHP 4.1.2) Date: Tue, 12 Mar 2002 19:44:13 -0600 X-Mailer: KMail [version 1.3.2] Cc: freebsd-security@FreeBSD.ORG References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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