From owner-freebsd-stable Thu Jan 18 19:46:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pinnacle.schulte.org (pinnacle.schulte.org [209.134.156.220]) by hub.freebsd.org (Postfix) with ESMTP id 36B2D37B400 for ; Thu, 18 Jan 2001 19:46:38 -0800 (PST) Received: (from schulte@localhost) by pinnacle.schulte.org (8.11.1/8.11.1) id f0J3jUI63243; Thu, 18 Jan 2001 21:45:30 -0600 (CST) (envelope-from schulte) Date: Thu, 18 Jan 2001 21:45:30 -0600 From: Christopher Schulte To: Christopher K Davis Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ports Message-ID: <20010118214530.A63218@schulte.org> References: <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ckd@ckdhr.com on Thu, Jan 18, 2001 at 10:02:23PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is what I've done when cvsup didn't properly update an older ports tree.... mv ports ports.old ; cvsup ports-supfile Causing, as you guessed, cvsup to pull down a freshly current ports tree. My only concern would be if I wanted to come back at a later date and modify a port which was installed from ports.old.... would the pkg_* suite still be able to recognize and deal with this? Are there other dependency issues which one should be aware? On Thu, Jan 18, 2001 at 10:02:23PM -0500, Christopher K Davis wrote: > Would a reasonable test/fix for this be deleting the entire port directory > in question and re-cvsupping? (This should make cvsup recreate everything > and update its file lists, right?) > > -- > Christopher Davis * * > Put location information in your DNS! -- christopher matthew schulte geek boy gone bad christopher@schulte.org http://www.schulte.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message