[comp.sys.apollo] More DSEE

Erstad@HI-MULTICS.ARPA (07/06/87)

With regards to Bill Jones' questions on specific DSEE capabilities:

> - is there support for maintaining, as Bob Reed mentioned, parallel
>   systems of derived objects, say one with debugging turned on and one
>   not?  Or will most of the binaries have to be recreated on each build
>   as the pool cache capacity is reached?

DSEE allows any number of parallel sets of derived objects to be 
retained.  A binary pool can be configured to set the maximum 
different flavors which may be retained for a single source 
object.  A time constraint may also be specified.  

> - in the above environment, what support is there for variant
>   implementations of the same module?  Must the elements be named
>   differently, and the system model preprocessed, to avoid conflict, or
>   can they be distinguished automatically in the directory structure?

The elements are all named the same - you are grabbing the same module, 
just a different version.  Directories are maintained automatically by
DSEE - typically you don't see them.  Versions may be specified by
number, "most recent", name, and/or branch (and combinations of the
above).

> - can a bug-fix or feature branch to several elements be treated
>   (e.g. named or merged) globally, or must the operations be repeated
>   for each element affected?

It can be named globally with no trouble.  The merge I'm not sure about.
 
> - can a system be composed of subsystems each maintained in its own
>   directory structure, or must there be a single system model (with
>   absolute pathnames) for the whole?

A system may be composed of multiple libraries, each of which could
correspond to a subsystem.  The system model does need to reference
all libraries by pathname, but this is not typically a problem
since the pathname to the library has nothing to do with which
element version you are accessing.

> - if the structure of the system is changed at some point in a way
>   which significantly affects the system model, will subsequent
>   modifications to earlier configurations see the new or old model?

Models can (and should) also be stored as DSEE elements.  Thus, 
you may use either the old or the new model, as appropriate.