From owner-freebsd-ports Thu Feb 8 9:29:12 2001 Delivered-To: freebsd-ports@freebsd.org Received: from jason03.u.washington.edu (jason03.u.washington.edu [140.142.8.11]) by hub.freebsd.org (Postfix) with ESMTP id 5D0F837B401; Thu, 8 Feb 2001 09:28:52 -0800 (PST) Received: from mead4.u.washington.edu (kraemer@mead4.u.washington.edu [140.142.12.172]) by jason03.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id JAA35818; Thu, 8 Feb 2001 09:28:48 -0800 Received: from localhost (kraemer@localhost) by mead4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id JAA46604; Thu, 8 Feb 2001 09:28:47 -0800 Date: Thu, 8 Feb 2001 09:28:47 -0800 (PST) From: Brian Kraemer To: freebsd-stable@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: Ports updating... Good ways? In-Reply-To: <200102081706.f18H6tj43176@bmah-freebsd-0.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What about extending "make" so that it is possible to do the following: $ cd /usr/ports/foo/bar $ make update "make" would then automatically deal with updating dependencies for that specific port, remove the old version and build the new one. I know this thread is mostly about updating all your ports at once, but this seems to be a good start. Using "make" in such a way ties in nicely with the current use of the ports system in my opinion. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message