fuel relies on the fact that the environment for materialization is the same as
where it has been serialized. So classes and methods need to be mostly the
same. A non-spur to spur change is likely to make it fail. These changes are
rare but sonetimes the need to be done. If you want to move data between
different environments you are better off using STON.
> Am 15.10.2016 um 23:28 schrieb Sean P. DeNigris <s...@clipperadams.com>:
> Sven Van Caekenberghe-2 wrote
>> AFAIU, Fuel is not capable working across versions, let alone over the
>> non-spur/spur divide. It's a let down, but it is by design (to optimise
>> for absolute speed).
> Lack of portability between Fuel versions is an annoyance, but is easy to
> overcome by updating Fuel on the source image to the same version as the
> target image before porting. But I don't see an obvious workaround for the
> non-spur -> spur breakdown. How can we leave users in a situation where it
> seems impossible to migrate data between Pharo versions?!
> View this message in context:
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.