From: Peter Raymond [mailto:Peter.Raymond@merant.com]
The statement in section 12 says:
"A configuration is a set of resources that consists of a root
collection and all members of that root collection that are not
members of another configuration."
So given the collection structure:
build
|
+----- include
|
+----- src
|
+----- gui
You cannot have a configuration rooted at build and another
configuration rooted at build/src.
What in the definition led you to this conclusion? (This is a real
question, not a rhetorical question, because if something in the text
led you to this conclusion, it should be fixed).
The statement you quote above just says that the members of the
nested (e.g. /build/src) configuration are not also members of the
parent (e.g. /build) configuration.
But later in section 12 it says:
"the root collection of a configuration can have a member that
is the root collection of one of its components"
So you can have a configuration rooted at build and a component
rooted at build/src.
Is my understanding of this correct?
Yes, your final conclusion (i.e. that nested configurations are
allowed) is correct.
Cheers,
Geoff