also ... ;-) we locked down the update stream because IIRC we discussed it being undefined for the Pharo image. Preferences showUpdateOptionInWorldMenu --> false
however, this is now our 1.0 release. we are happy to push this out without any ability for users to update it? the core and pharo (dev) images can have their own sections in the update.list. we could define two separate sections and then we leave ourselves open to push updates out to Pharo 1.0 if we want to? or are we just going to push out updates to PharoCore 1.0 at this stage in our process? i imagined such an update to Pharo 1.0 would be a carefully crafted metacello/gofer script. thanks. enough questions for now! Mike _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
