From owner-freebsd-current Fri Nov 8 13:52:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 080DA37B401 for ; Fri, 8 Nov 2002 13:52:18 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-146.dsl.lsan03.pacbell.net [63.207.60.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7368143E3B for ; Fri, 8 Nov 2002 13:52:17 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 55F1366B5E; Fri, 8 Nov 2002 13:52:16 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 95426113D; Fri, 8 Nov 2002 13:53:53 -0800 (PST) Date: Fri, 8 Nov 2002 13:53:53 -0800 From: Kris Kennaway To: Ray Kohler Cc: kris@obsecurity.org, current@FreeBSD.ORG, mark@grondar.org Subject: Re: perl5.6.1 wrapper Message-ID: <20021108215352.GA26821@rot13.obsecurity.org> References: <20021108210249.GA26345@rot13.obsecurity.org> <200211082122.gA8LMO1a080022@arkadia.nv.cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200211082122.gA8LMO1a080022@arkadia.nv.cox.net> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Nov 08, 2002 at 04:22:24PM -0500, Ray Kohler wrote: > > From owner-freebsd-current@FreeBSD.ORG Fri Nov 8 16:15:05 2002 > > Date: Fri, 8 Nov 2002 13:02:58 -0800 > > From: Kris Kennaway > > To: Ray Kohler > > Cc: kris@obsecurity.org, mark@grondar.org, current@FreeBSD.ORG > > Subject: Re: perl5.6.1 wrapper > > > > On Fri, Nov 08, 2002 at 06:54:37AM -0500, Ray Kohler wrote: > > > > > Then we're back to the problem of there being a complete stale perl in > > > the base system after a 4.X->5.X upgrade, but then, I've always thought > > > that "clean out the cruft" ought to be a mandatory step in upgrading. > > > > Yes, it's already a mandatory step (remove old includes, or you can't > > build C++ programs). > > I mean *all* the cruft -- old modules and config files, deprecated binaries > and man pages, even old shlibs if it's safe. I agree with you, and I was giving an example that a lesser form of this is already required during the upgrade. It would be VERY useful if someone could develop a script to do this (e.g. install various versions of 4.x and do an upgrade, then collect a complete list of all the stale files). Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message