From owner-freebsd-current Wed Apr 5 13:13:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA27562 for current-outgoing; Wed, 5 Apr 1995 13:13:17 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA27546 for ; Wed, 5 Apr 1995 13:12:52 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA29572; Thu, 6 Apr 1995 06:12:14 +1000 Date: Thu, 6 Apr 1995 06:12:14 +1000 From: Bruce Evans Message-Id: <199504052012.GAA29572@godzilla.zeta.org.au> To: nate@sneezy.sri.com, terry@cs.weber.edu Subject: Re: NOTICE: If you care, speak now! Cc: current@FreeBSD.org, phk@ref.tfs.com, rkw@dataplex.net Sender: current-owner@FreeBSD.org Precedence: bulk >> > 3) This is no more of a change than the changes to "install" that are being >> > so widely advocated. >> >> Huh? The install change affects *one* utility, but the changes you are >> advocating effect the entire build process, and from the sounds of it >> every Makefile. And, as a rebuttal, even though the install changes are >> to one tool, because of the significance of the tool those changes might >> not make it into the release. >Oh, ho, he's got you, Nate! That one utility is used to install all the >binaries on the system. 8-). The new flags would have no effect if they weren't used. It's very easy to support the new flags without affecting the current build process if you don't want to: + change `install' + fix some system makefiles that suffer from bitrot: bsd.doc.mk, bsd.info.mk and bsd.man.mk are missing support for ${INSTALLFLAGS}. Users who wish to use the new flags can type make INSTALLFLAGS='-newflag1 =newflag2 ...' If most developers like this then we can change the makefiles to always use the new flags (headers and libararies should be installed without changing the target timestamp if possible). Bruce