From owner-freebsd-hackers Tue Apr 4 16:51:45 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA26765 for hackers-outgoing; Tue, 4 Apr 1995 16:51:45 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA26758 for ; Tue, 4 Apr 1995 16:51:40 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id RAA08239; Tue, 4 Apr 1995 17:55:25 -0600 Date: Tue, 4 Apr 1995 17:55:25 -0600 From: Nate Williams Message-Id: <199504042355.RAA08239@trout.sri.MT.net> In-Reply-To: "Rodney W. Grimes" "Re: new install(1) utility" (Apr 4, 3:43pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Rodney W. Grimes" Subject: Re: new install(1) utility Cc: freebsd-hackers@freefall.cdrom.com Sender: hackers-owner@FreeBSD.org Precedence: bulk [ Smarter intall which only installs files if they have changed ] > > And, if we pre-build the compressed man-pages, we can do the comparisons > > at install time to determine if they need to be installed or not. > > This is actually fairly easy to fix, and it should be. Doing the gzip > in the installed man page area really trashes my /usr file system!! We are in agreement here? Wow! > Also, I am of the opinion that the only thing being done during the > install phase is INSTALLING, not gzipping or otherwize munging files! > > Almost to the point of having a ${PROG}.stripped rule (you'r cmp thing > in install is going to have to compare a stripped version of programs > or it will always fail for the standard binary case). Hmm, I had forgotten about the strip option. Sigh.. However, for the parts of the system that bite us the most the smart install is a good solution. We don't have to use it for everything (or anything for that matter), but for those files which do affect the dependencies, I think it would be a big win. Nate