From owner-freebsd-hackers Fri Feb 17 03:26:52 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id DAA04665 for hackers-outgoing; Fri, 17 Feb 1995 03:26:52 -0800 Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id DAA04657; Fri, 17 Feb 1995 03:26:47 -0800 Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.9/8.6.9) with SMTP id FAA21337; Fri, 17 Feb 1995 05:26:45 -0600 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 17 Feb 1995 05:26:46 -0600 To: "Jordan K. Hubbard" From: rkw@dataplex.net (Richard Wackerbarth) Subject: Building Tree from read-only, etc. Cc: hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk As I stated a while back, I want to be able to have a "make world" that can use a cd rom version of the tree, allow multiple users to work on different versions at the same time, and NOT mess with the running system environment. I have managed to work out a system that will allow the parallel existance of source and object trees. I can even handle symbolic links to directories (a "bitch"). In order to do this, I had to really "muck" with the MAKEOBJDIR env variable. (Too many extra "shells" to suit my taste). I see 4 possibilities. 1) Forget it! Use the status quo. (I don't like that one) 2) Use the extra shells (Messy, slow) 3) Alter "make" to properly accept a command line argument rather than (in addition to) the shell env variable. 4) Let people use the "cloned tree of symbolic links" approach with the objects in the tree. Personally, I prefer "3", but I don't know how people would feel about alterations to "make". "4" has the advantage that you do not need special utilities/procedures to move parts of trees around. It also has a number of drawbacks. Suggestions? Direction.. ---- Richard Wackerbarth rkw@dataplex.net