On Fri, Nov 08, 2002 at 04:22:24PM -0500, Ray Kohler wrote: > > From [EMAIL PROTECTED] Fri Nov 8 16:15:05 2002 > > Date: Fri, 8 Nov 2002 13:02:58 -0800 > > From: Kris Kennaway <[EMAIL PROTECTED]> > > To: Ray Kohler <[EMAIL PROTECTED]> > > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] > > 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
