From owner-freebsd-security Wed Mar 13 11:31:48 2002 Delivered-To: freebsd-security@freebsd.org Received: from mail.enic.cc (lobo.nic.cc [206.253.214.247]) by hub.freebsd.org (Postfix) with ESMTP id 1194F37B404 for ; Wed, 13 Mar 2002 11:31:46 -0800 (PST) Received: from smokey.lan.enic.cc (tailback [206.253.214.252]) by mail.enic.cc (Postfix) with ESMTP id AD6F36A916 for ; Wed, 13 Mar 2002 11:31:45 -0800 (PST) Subject: Re: Managing port security upgrades (was:Re: PHP 4.1.2) From: Mark Foster To: freebsd-security@FreeBSD.ORG In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 13 Mar 2002 11:31:45 -0800 Message-Id: <1016047905.6825.34.camel@smokey.lan.enic.cc> Mime-Version: 1.0 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 Sounds alot like pkg_version -c -v | sh (assuming an updated ports tree) On Wed, 2002-03-13 at 11:07, batz wrote: > On Wed, 13 Mar 2002, Adam Wight wrote: > > :What about a new make target, "upgrade," that only sync'ed the ports > :subtree for the port being built and its dependencies? > > Hrm, so it would be implemented in the makefiles of the entire ports > collection? A top level makefile or one in each port? > > I was thinking about this a bit more, and it occured to me that > using /var/db/pkg as a reference point, and either sup'ing a new > port, which would then get a sort of 'reverse dependancies' list, > from /var/db/pkg/portname/+REQUIRED_BY, and selectively upgrading > anything in there which had the original port as a dependancy. > > That sounds like it might run into problems with recursion, thoughts? > > > > -- > batz > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message -- -mdf [Mark D. Foster] Phone: 206-381-0449 System Administrator - eNIC Corporation Fax: 206-329-7107 or mergatroid on AIM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message