From owner-freebsd-current Tue May 14 7:15:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2997437B406; Tue, 14 May 2002 07:15:51 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id AAA00607; Wed, 15 May 2002 00:15:49 +1000 Date: Wed, 15 May 2002 00:18:04 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Ruslan Ermilov Cc: current@FreeBSD.ORG Subject: Re: make includes In-Reply-To: <20020514133456.GD81899@sunbay.com> Message-ID: <20020515001124.Y4301-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 14 May 2002, Ruslan Ermilov wrote: > On Tue, May 14, 2002 at 11:32:19PM +1000, Bruce Evans wrote: > > Installing includes just corrupts the host environment unless the new > > includes are consistent with the old libraries. If you know the build > > system, the includes and the libraries well enough to know when it is > > safe to use, then you know enough to never need it. > > > People might want to use it like that: > > make world > mv /usr/include /usr/include.old > make incsinstall > > To remove stale includes. Previous version had "includes" that both > built and installed includes, I have just split it in two parts. That's rather hackish, and doesn't handle garbage other than includes. I usually find stale files by comparing my world with a world installed in a nonstandard DESTDIR. A mergemaster-like utility could automate this. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message