From owner-freebsd-ports Thu Jan 15 14:14:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16815 for freebsd-ports-outgoing; Thu, 15 Jan 1998 14:14:31 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@rtfm.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16782 for ; Thu, 15 Jan 1998 14:14:27 -0800 (PST) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id RAA12973; Thu, 15 Jan 1998 17:14:28 -0500 (EST) Message-ID: <19980115171427.46891@rtfm.net> Date: Thu, 15 Jan 1998 17:14:27 -0500 From: Nathan Dorfman To: ports@FreeBSD.ORG Subject: Upgrading Ports Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is pkg_deleting a port and then reinstalling it the best/only way to upgrade a port when the software involved has gone up a version? If so, maybe the packing list should mark some files as ``hard'' that should stay after a pkg_delete, perhaps if a ``keep hard'' flag has been given. For ports that install stuff that should stay across an upgrade. -- ________________ _______________________________ / Nathan Dorfman V PGP: finger nathan@rtfm.net / / nathan@rtfm.net | http://www.rtfm.net /