From owner-freebsd-questions@FreeBSD.ORG Fri Mar 25 21:43:24 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0476516A4CE for ; Fri, 25 Mar 2005 21:43:24 +0000 (GMT) Received: from post5.inre.asu.edu (post5.inre.asu.edu [129.219.110.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id D463943D2F for ; Fri, 25 Mar 2005 21:43:23 +0000 (GMT) (envelope-from David.Bear@asu.edu) Received: from conversion.post5.inre.asu.edu by asu.edu (PMDF V6.1-1X6 #30769) id <0IDX00I01GAQ8S@asu.edu> for freebsd-questions@freebsd.org; Fri, 25 Mar 2005 14:42:26 -0700 (MST) Received: from smtp.asu.edu (smtp.asu.edu [129.219.110.107]) by asu.edu (PMDF V6.1-1X6 #30769) with ESMTP id <0IDX00EKUGAQXW@asu.edu> for freebsd-questions@freebsd.org; Fri, 25 Mar 2005 14:42:26 -0700 (MST) Received: from moroni.pp.asu.edu (moroni.pp.asu.edu [129.219.69.200]) (8.12.10/8.12.10/asu_smtp_relay,nullclient,tcp_wrapped) with ESMTP id j2PLgQMC020430 for ; Fri, 25 Mar 2005 14:42:26 -0700 (MST) Received: by moroni.pp.asu.edu (Postfix, from userid 500) id E787810D1; Fri, 25 Mar 2005 14:42:26 -0700 (MST) Date: Fri, 25 Mar 2005 14:42:26 -0700 From: David Bear To: freebsd-questions@freebsd.org Message-id: <20050325214226.GE25901@asu.edu> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.4.1i Subject: portupgrade overview X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David.Bear@asu.edu List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2005 21:43:24 -0000 I've used portupgrade for a while without really knowing much about it. I suppose thats a benefit. However, when it comes to really controlling the portupgrade processes, I find the man page of minimal use. Thats becuase the man pages seem to be written for someone who already knows everything that portupgrade is doing, ie there seems to be a lot of a priori knowledge expected of the reader. I am hoping there is better documentation of portupgrade. Something that specifies the reasons behind what it does -- why some of the switches are necessary, how to hold back upgrade of certain ports, how to only allow security updates to happen, etc. Does any such document exist? -- David Bear phone: 480-965-8257 fax: 480-965-9189 College of Public Programs/ASU Wilson Hall 232 Tempe, AZ 85287-0803 "Beware the IP portfolio, everyone will be suspect of trespassing"