Stef, I am not sure I know enough to have an opinion. You mentioned slices before in response to my concerns over saving individual packages. If that is a fix, great. I have been taking a different approach, along the lines of Migrate, which I wrote for Dolphin. It is different for Pharo, and (so far anyway) not as slick, but some of the features that made sense in Dolphin might not be needed in Pharo. The essential features include: (1) search for code that I wrote and is not yet in one of my packages (meaning it is at risk of being lost in a move) (2) allow a "global save" of all packages of interest - this is the newest feature, and I *think* it works (3) load the saved packages into a new image; the loader is installed first and then launched to search for what it needs (it complains early when possible) and then loads the packages. There MUST be a better way :) I had to do something, because chasing after lost work was driving me nuts. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stéphane Ducasse Sent: Wednesday, November 04, 2009 10:06 AM To: Pharo Development Subject: [Pharo-project] Slice and others Hi guys I would like to generalise the slice ideas so that even if you publish a single package change you use a slice because I'm spending time to look for these simples changes in single packages. What do you think? Stef _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project