This is an observation of what seems like quirky behavior of the &lt;conditional&gt;@somerule feature.<br><br>I am trying to use stage.install in the following manner:<br><br>install dummy1 : $(some-files) : &lt;conditional&gt;set-install-loc &lt;subdir&gt;xxx ;<br><br>install dummy2 : $(other-files) : &lt;conditional&gt;set-install-loc &lt;subdir&gt;yyy ;<br><br>(I talked about the need for unique dummy[x] names in a different thread.)<br><br>The &lt;subdir&gt; feature is intended to be used by my set-install-loc rule to add&nbsp; subdir (xxx, yyy, etc.)&nbsp; to the path (which includes other stuff gotten dynamically).<br><br>rule set-install-loc ( properties * )<br><br>I was hoping that set-install-loc would be called separately for dummy1 and dummy2, but this is not the case.&nbsp; It gets invoked as follows:<br><br>1.&nbsp; $(properties) has no &lt;location&gt; attribute; has &lt;subdir&gt;xxx.&nbsp; Results are $(properties) &lt;location&gt;blah/blah/xxx<br><br>The
 next callback, I think, is made to ensure that properties are stable:<br><br>2.&nbsp; $(properties) has &lt;location&gt;blah/blah/xxx and &lt;subdir&gt;xxx.&nbsp; Results are $(properties)<br><br>There are no further callbacks to set-install-loc, as expected, for install dummy2, where I was hoping/expecting there to be no &lt;location&gt; attribute and &lt;subdir&gt;yyy.<br> <br>The workaround is to have separate callback rules &lt;conditional&gt;@set-install-loc-xxx and &lt;conditional&gt;@set-install-loc-yyy that&nbsp; manage putting xxx and yyy subdirs in the install path.<br><br>FWIW and HTH someone else down the road,<br>Mark<br>