|(no subject) [message #723071 is a reply to message #722996]
||Wed, 07 September 2011 10:47
| Henrik Lindberg
Registered: July 2009
Feature imports are by definition supposed to be specified by some other
entity or it would not be possible to create variation of the
composition without changing the feature itself.
In different words:
When you have feature imports (or bundle package imports), you need a
component that defines what to actually use. In some cases this is a
"product" of some sort, in other cases, there is no natural starting
point (or you have multiple starting points). In those cases, we
typically use the "releng" project itself as the root component, and
describe the configuration of all components that can not be derived
from the transitive scope of features/bundles.
We typically do this with a .cspex. (You could also create a feature
that contains the features you want in your configuration if you prefer
Hope that makes it clearer.
On 9/7/11 1:42 PM, Thorsten Meinl wrote:
> Is there a reason why Buckminster does not resolve feature imports in
> features (aka feature dependencies,<import...>)? It only resolves
> included features (<includes..>).
Powered by FUDForum
. Page generated in 0.01526 seconds