<br><br><div class="gmail_quote">On Thu, Aug 2, 2012 at 1:13 PM, Levente Uzonyi <span dir="ltr"><<a href="mailto:leves@elte.hu" target="_blank">leves@elte.hu</a>></span> wrote:<br><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We can't remove updates from Trunk without breaking all updated images, so that won't work (we don't want to break the "update button"). </blockquote>
</div></blockquote><div><br></div><div>That's why I suggested adding a new update that removes environments if they're present. (Perhaps removing 216 really means replacing it with a no-op.) So images that haven't been updated yet, will get a pair of no-ops, while updated images will get a new update that reverses the previous one. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So, going forward is the way to do it. Push a new versions of the packages which simply revert the changes. If something has to be unloaded, then bump the version number of the VersionNumber package to ensure that the update number will be</blockquote>
</div></blockquote><div><br></div><div>Sure, for updated images we reverse the previous changes. But I'd like to leave the existing SystemDictionary in place for un-updated images if we can manage it.</div><div><br></div>
<div>Colin </div></div><br>