From owner-freebsd-hackers Wed Jul 25 7:59:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 55C5937B800 for ; Wed, 25 Jul 2001 07:58:05 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f6PEw3F60656; Wed, 25 Jul 2001 08:58:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f6PEw3o07608; Wed, 25 Jul 2001 08:58:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107251458.f6PEw3o07608@harmony.village.org> To: Sheldon Hearn Subject: Re: Why install -C include files? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 25 Jul 2001 16:54:14 +0200." <6000.996072854@axl.seasidesoftware.co.za> References: <6000.996072854@axl.seasidesoftware.co.za> Date: Wed, 25 Jul 2001 08:58:02 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <6000.996072854@axl.seasidesoftware.co.za> Sheldon Hearn writes: : : : On Wed, 25 Jul 2001 08:48:36 CST, Warner Losh wrote: : : > : Why are include files installed using -C instead of -c? This makes it : > : harder to find stale includes. : > : > I've wanted to have a /etc/mtree/bsd.obsolete for a long time now... : : That would make me too nervous. All I really want is the assurance that : ``make world'' updates the mtime of every file it would have installed : if not present at install time. : : With revived CLOBBER support and COPY=-c, the only problem children are : symbolic links. Everything else can be hunted down with find -mtime X. The reason I'd like to see it isn't so that make world kills things automatically, but so that I could kill them (or at least find out what should be killed) on systems that had FreeBSD 1.0 installed on them, then upgraded, disk cloned, etc. At one point I had 4 machines that were created by this method from my original FreeBSD installation. However, I don't think I have anything further back than 2.2.8 or 3.2 as the base of a system right now due to EOL on spinning media, lapses in backup discipline, etc. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message