> Metacello supports both, but not at the same time. Either you mark your configuration with fixed versions (best for patches) or with symbolic versions (best for releases).
<br/>I don't understand this. If you don't want your dependencies upgraded, you don't change the versions referenced in your new version, if you do, you manually change them. Either way, you make a new version, whether it's a patch, enhancement, or total overhaul.
<br/><br/>The symbolic versions, OTOH, map your versions to their status on respective platforms. You would do this for every new version.

	
	
	<div class="signature" style="margin-top:1em;color:#666666;font-size:11px;">
				Cheers,
<br/>Sean
			</div>
<br/><hr align="left" width="300" />
View this message in context: <a href="http://forum.world.st/Metacello-configuration-conventions-tp4681777p4682563.html">Re: Metacello configuration conventions</a><br/>
Sent from the <a href="http://forum.world.st/Pharo-Smalltalk-f1294837.html">Pharo Smalltalk mailing list archive</a> at Nabble.com.<br/>