From owner-freebsd-questions@FreeBSD.ORG Mon May 23 13:30:49 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 256BC16A41F for ; Mon, 23 May 2005 13:30:49 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail25.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id D111943D53 for ; Mon, 23 May 2005 13:30:48 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 25867 invoked from network); 23 May 2005 13:30:48 -0000 Received: by simscan 1.1.0 ppid: 25858, pid: 25862, t: 0.1321s scanners: clamav: 0.84/m:31/d:888 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail25.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 May 2005 13:30:48 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 7196030; Mon, 23 May 2005 09:30:47 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Bob Perry References: <200505221429.58567.rperry@gti.net> From: Lowell Gilbert Date: 23 May 2005 09:30:47 -0400 In-Reply-To: <200505221429.58567.rperry@gti.net> Message-ID: <44sm0e133s.fsf@be-well.ilk.org> Lines: 13 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Confused with Refuse X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2005 13:30:49 -0000 Bob Perry writes: > About to synch up the entire source tree with RELENG_5_4_0_RELEASE. Earlier I > created a refuse file, (/var/db/sup/refuse), when I upgraded my doc and ports > collection in 5.3 but remember reading somewhere that a refuse file was not > necessarily recommended when updating an entire source tree. Is that still > the case? You may not be able to build your own INDEX, and dependency-tracking packages may get confused if the INDEX doesn't match the installed ports, but things won't necessarily break. But you're on your own; please don't report problems unless you know they occur with a fully updated tree.