Re: New host challenges: libraries

[Will P. <pa...@dc...>]

Joel S raises some valid things-that-could-be-better; on
this one...

> ... The problem is that the <configure> method runs only
> on the gold host. It is not rerun for each new host, so
> the constraints are ignored. I added the same three
> constraints to the <deploy> method as a workaround. ...
> 
> Although repeating the constraints in <configure> and
> <deploy> appears to work, it seems awkward. Shouldn't
> there be a way to specify these constraints only once?

Does the idiom below (untested) give you any joy?

Will

<configure>
  <constraint><dependency type="normal" name="." on-method="common-constraints" /></constraint>
  ...
</configure>

<deploy>
  <constraint><dependency type="normal" name="." on-method="common-constraints" /></constraint>
  ...
</deploy>

<common-constraints>
  <constraint><dependency type="normal" name="library1" on-method="deploy" /></constraint>
  <constraint><dependency type="normal" name="library2" on-method="deploy" /></constraint>
  <constraint><dependency type="normal" name="library3" on-method="deploy" /></constraint>
  <code lang="none" recordable="no" />
</common-constraints>