From owner-freebsd-current Wed Feb 22 14:10:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA05697 for current-outgoing; Wed, 22 Feb 1995 14:10:07 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id OAA05684; Wed, 22 Feb 1995 14:10:00 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id OAA05455; Wed, 22 Feb 1995 14:09:32 -0800 From: Poul-Henning Kamp Message-Id: <199502222209.OAA05455@ref.tfs.com> Subject: Re: TRUE and FALSE To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Wed, 22 Feb 1995 14:09:32 -0800 (PST) Cc: wollman@halloran-eldar.lcs.mit.edu, current@freefall.cdrom.com In-Reply-To: <5415.793490429@freefall.cdrom.com> from "Jordan K. Hubbard" at Feb 22, 95 02:00:29 pm Content-Type: text Content-Length: 802 Sender: current-owner@FreeBSD.org Precedence: bulk > To put it another way, the /usr/include directory follows NO > consistent paradigm - some things are links, others are copies of > stuff, still others are just pointers into the sources. If you make > with SHARED=copies then this unifies some of it by copying stuff > across, but it could then be argued that the "non-copies" case should > see /usr/include as *only* a link farm, with no actual files in there. I belive this can be dealt with in one stroke. Since we want (as a medium term goal) to have our source compile without reference to /usr/include, then we will not need the links, and we can safely and decisively remove the SHARED!=copies case. -- Poul-Henning Kamp TRW Financial Systems, Inc. I am Pentium Of Borg. Division is Futile. You WILL be approximated.