From owner-freebsd-current  Thu Sep 18 23:43:31 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA18277
          for current-outgoing; Thu, 18 Sep 1997 23:43:31 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (ala-ca26-26.ix.netcom.com [207.93.42.90])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA18272
          for <freebsd-current@FreeBSD.ORG>; Thu, 18 Sep 1997 23:43:27 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id XAA10791; Thu, 18 Sep 1997 23:43:20 -0700 (PDT)
Date: Thu, 18 Sep 1997 23:43:20 -0700 (PDT)
Message-Id: <199709190643.XAA10791@silvia.HIP.Berkeley.EDU>
To: gurney_j@resnet.uoregon.edu
CC: dima@tejblum.dnttm.rssi.ru, freebsd-current@FreeBSD.ORG
In-reply-to: <19970918213446.00164@hydrogen.nike.efn.org> (message from John-Mark Gurney on Thu, 18 Sep 1997 21:34:46 -0700)
Subject: Re: Yet Another bug in src/Makefile
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * why should it remove /usr/include??  /usr/include is not used for the
 * building of the resulting binaries install.. why not do a rm -rf /
 * if you want to clean out the area your installing to... :)
 * 
 * of course there is good argument that the installed to area should
 * be clean to prevent old files from contaminating a setup...  but
 * if we start to clean out /usr/include, we should also do /{bin,sbin}
 * /usr/{bin,share,sbin,lib,libexec} and any others that get installed...

I agree with you, but the comments at the top of src/Makefile say
otherwise.  Should we just nuke the CLOBBER option entirely, or change 
the rules so it will actually delete /usr/include/*?

Satoshi