Path: utzoo!attcan!uunet!lll-winken!ames!sun-barr!texsun!texbell!bigtex!milano!lad-shrike!aihaug
From: aihaug@AUSTIN.LOCKHEED.COM (Daniel A Haug)
Newsgroups: comp.lang.lisp
Subject: Re: Unix Lisp Environments (why the slow evolution)
Summary: what about configuration maintenance
Message-ID: <260@shrike.AUSTIN.LOCKHEED.COM>
Date: 12 May 89 04:56:44 GMT
References: <8905111806.AA05209@snooze>
Organization: Lockheed Austin Div.
Lines: 35

> Brad,
>   Yes we have *true* stack groups which share everything (but stack,
> obviously)--there is one UNIX process.  All the features of our
> debugger work generally on any `lightweight lisp' process (LLP), which
> means you can return, restart, examine locals, etc.  In fact, Allegro
> Common Windows uses one LLP for each window.  

I must admit that this is much further advanced than I had previously
expected.  I, too, am seeking more information.  To that end, what
about a maintenance utility equivalent to the System Construction Tool
on the Symbolics?  This includes tracking system-level and file-level
versions, and support for an extensive Patch facility?  I've already
heard Apollo talking about their `make'-equivalent system.  This is
no good if it can't retain and track specific file versions, and
system versions.  Along this line would be distribution/restoration
of systems (I'm talking about something more than `tar' -- the ability
to generate a system distribution for a specific version, with all the
patches, sources, etc., in a single command).  I've also seen a few
public domain defsystem packages.  But, what I've seen so far doesn't
even come close to what we need.

My motivation?: our project is now several hundred thousands of lines of
code in size.  We have several subcontractors, and we exchange systems
back and fourth on a daily basis.  We would DIE without the configuration
management capabilities provided by SCT.  We also support several
additional sites with full software suites, and some sites with restricted
suites (e.g. no sources).  We do this all currently with half a person.

What about ``advising'' functions?  I could live without it... but it
has proved itself as an excellent debugging tool.

Dan Haug

Internet: haug@austin.lockheed.com
uucp:     ut-emx!lad-shrike!aihaug