From owner-freebsd-current Fri Jun 26 02:48:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10930 for freebsd-current-outgoing; Fri, 26 Jun 1998 02:48:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10883 for ; Fri, 26 Jun 1998 02:48:09 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id CAA12747; Fri, 26 Jun 1998 02:48:40 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: jbryant@unix.tfs.net cc: freebsd-current@FreeBSD.ORG Subject: Re: schg flags in the source/object tree... bullsh**! In-reply-to: Your message of "Fri, 26 Jun 1998 01:31:37 CDT." <199806260631.BAA21770@unix.tfs.net> Date: Fri, 26 Jun 1998 02:48:39 -0700 Message-ID: <12743.898854519@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > what was the compelling idea behind all of the schg flags in /usr/obj? I never thought of it as a compelling idea so much as a "gee, we can fix the host interdependency problem by setting DESTDIR to point elsewhere for the first pass" sort of idea. Since the install rules for everything deal with immutability on the targets, things in /usr/obj become immutable as a consequence. "Fixing" this would also probably require more grossness in the installation targets than the problem warrants. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message