cedreek wrote > So is it possible to define such constraints ? IIUC you could use #onConflict: and be more specific in the block as to allow only the specific case you mentioned, but I think the more common approach is to use the Metacello API to "lock" NeoJSON to the version you want. I don't have an image handy, but search either the Pharo or Metacello MLs for "API lock" or something
cedreek wrote > Still, not sure, of the meaning of #useIncoming (#allow #disallow). Browse MetacelloResolveProjectUpgrade. There are several synonyms for the same action. IIRC #allow et all means continue to load replacing the currently loaded version, #disallow means use the version already loaded. cedreek wrote > 2) is it possible to launch such Metacello installation from Iceberg ? I don't see why you couldn't put the API lock into a preloadDoit in your baseline A context shift is definitely required to get a handle on this, but after the initial investment, it's pretty straightforward. There are a few concepts applied repeatedly in most common cases. Hang in there! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
