From owner-freebsd-ports Thu Jan 15 16:08:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29682 for freebsd-ports-outgoing; Thu, 15 Jan 1998 16:08:24 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from ppp6465.on.bellglobal.com (ppp1718.on.bellglobal.com [206.172.249.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29677 for ; Thu, 15 Jan 1998 16:08:19 -0800 (PST) (envelope-from ac199@hwcn.org) Received: from localhost (tim@localhost) by ppp6465.on.bellglobal.com (8.8.8/8.8.8) with SMTP id TAA01067; Thu, 15 Jan 1998 19:04:10 -0500 (EST) (envelope-from ac199@hwcn.org) X-Authentication-Warning: ppp6465.on.bellglobal.com: tim owned process doing -bs Date: Thu, 15 Jan 1998 19:04:10 -0500 (EST) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Nathan Dorfman cc: ports@FreeBSD.ORG Subject: Re: Upgrading Ports In-Reply-To: <19980115171427.46891@rtfm.net> 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 On Thu, 15 Jan 1998, Nathan Dorfman wrote: > 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? "best". Files from an old version may potentially become unnecessary. > 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. Can you name an example of something that should stay across an upgrade? Potentially important configuration files should already be left alone, I believe. Taking the opposite (but equivalent) of your idea, marking certain files (or types of files, such as ~/.pkgname for every user) as "to be deleted on a `hard' delete" is, I believe, a twisting ugly road that will run over people's feet. If I pkg_delete perl5, should all the perl5 scripts I've written be found and deleted? -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster.