I have been looking at the (horribly named) #timeStamp of methods; if my initials/name appear a substring, then it's a red flag that I might have written it, or at least want to be alerted that I might have unpackaged efforts. The following is a first attempt at releasing the code I use to save a later load packages:
http://squeaksource.com/PharoInbox/Migrate-Core-BillSchwab.2.mcz It might not work w/o my stream extensions and other infrastructure - fair warning. If remotely interested, look at the class comment of Migrate; expect to subclass it and override a few methods (#me, #homeGrownPackages) to get it to do anything meaningful. This design allows me to distribute its core functionality but have my own concrete class that is not for public viewing. The #suspectMethodsReport might be of interest to you. Bill ________________________________________ From: pharo-project-boun...@lists.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Hernán Morales Durand [hernan.mora...@gmail.com] Sent: Tuesday, August 31, 2010 4:29 PM To: Pharo Development Subject: [Pharo-project] Distinguishing system and user objects Hi guys, Given any Pharo image and a (any) package or class category, how do you find if the package/class category belongs to the official image release? Thanks, Hernán _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
