Hi Stephan, We have a reliable and working solution to achieve this, even if it gives a strong feeling of being ad-hoc. We develop Roassal in Pharo. Roassal on Pharo has essentially two .mcz packages: Roassal.mcz and RoassalMorphic.mcz. So, you have two packages listed in the configuration and in the Monticello browser. We then have a method: =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= ROExporter>>toVW " self new toVW If I'm executed, I generate a st file called Roassal-AlexandreBergel.(*version*)-vw5.st near to the image (./contents/resources). To import Roassal in VW your should have a Roassal version already loaded in the image and follow this steps: 1) Remove the Roassal-Core package and agree with all the classes removal in the Roassal-VWSpecific. 2) Create the Roassal-Core package again and do right click in the package, select 'file into' and choose the file you exported. 3) FInally restore the Roassal-VWSpecific package by loading the latest version of it from the public repository. " Gofer new squeaksource: 'PackageInfo'; package: 'PackageInfo-Exporters'; load. (Smalltalk at: #VW5PackageExporter) fileOutPackageNamed: 'Roassal' withNamespace: 'Roassal'. =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= =-=-=-=-=-= Cheers, Alexandre On Sep 27, 2012, at 7:59 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.