This thread may help you: http://forum.world.st/Fuel-version-td4823170.html
Cheers, On Thu, May 28, 2015 at 9:19 PM, Ben Coman <b...@openinworld.com> wrote: > On Fri, May 29, 2015 at 7:17 AM, Sean P. DeNigris <s...@clipperadams.com> > wrote: > > Peter Kenny wrote > >> I will have to convert all my files to the new version? As far as I can > >> see, I could not do that using > >> the device you suggest > > > > The thing is that it's only the serialization that is tied to a Fuel > > version, so the workflow is (and I've done this to port my data from > Pharo > > 3.0 to Pharo 4.0 and then to Pharo 5.0): > > > > 1. In the older image with the data, upgrade Fuel to the latest version > that > > will load in that Pharo `ConfigurationOfFuel project stableVersion load` > > This does not cater for "storing object structures long term on > disk." I guess the workaround is that the image used to store the > objects needs to archive near the fuel files. But you'd need to be > careful not to save it once you upgraded fuel versions. > > > 2. Serialize the data > > If the Fuel version in #1 is the one that comes with the newer Pharo > you're > > porting to, you're done. You can now materialize in the newer Pharo > version. > > Otherwise... > > 3. In the newer Pharo > > a. Downgrade Fuel e.g `(ConfigurationOfFuel project version: > > versionStringFromNumberOneAbove) load` > > b. Materialize the data > > c. Upgrade Fuel back to the normal version for the newer Pharo (replace > > version string from 3.a. with the original version) > > d. Serialize the data > > Some use cases may require multiple downgrades/upgrades, which could > be annoying. An interesting idea might be for a new release of Fuel to > rename the previous version of as OldFuel that is released in its own > package. Then "some OldFuel version" could exist in parallel with the > "current version." The "current version" might even be smart enough to > identify the OldFuel version needed and load it into the image and > continue materializing the data. A CI program might run through a > range of OldFuel versions to track which remain working on future > versions of Pharo. > cheers -ben > > > > > Now you can load the data into the newer Pharo. > > > > > > Peter Kenny wrote > >> could I set those to give different version numbers > > > > The problem is that the data format may not be compatible between the > > versions. Mariano would be able to give a better answer, but I would be > > afraid. What if it seems to work but corrupts your data?! > > > > > Does the workflow I detailed make sense and cover your needs? > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/How-to-move-data-between-Pharo-versions-tp4829102p4829210.html > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > -- Mariano http://marianopeck.wordpress.com
