Ok I will I do not have the snipped at hand that can check all the dirty methods. Could you add that to bug traker with a request for feature because indeed this is a nice one.
Stef On Sep 20, 2009, at 8:24 AM, Schwab,Wilhelm K wrote: > Stef, > > I've done that, but my understanding is that "all" it does is show > the methods that are packaged. I am hoping for something that would > sniff out the methods that I have altered and are not in packages > that I (somehow) claim to own. It seems like it would be really > easy to miss important work and that it should be relatively easy to > create something that scans for at-risk code. One thing I can > enivision would compare a list of packages with user-owned methods > in the system; anything that is not in one of the packages goes in a > method browser with commands to package them in likely places. > > Bill > > > -----Original Message----- > From: [email protected] > [mailto:[email protected] > ] On Behalf Of Stéphane Ducasse > Sent: Sunday, September 20, 2009 1:03 AM > To: [email protected] > Subject: Re: [Pharo-project] Gofer vs Installer > > The first thing you can try is to check using the browse button of > MC that you extensions methods are well in your package. > > Stef > > On Sep 20, 2009, at 12:43 AM, Schwab,Wilhelm K wrote: > >> I'd like to put on my user hat for a moment. A big concern of mine >> is >> doing a good job of saving packages from one image and moving them to >> another. I have (hopefully) been keeping my install script current >> as >> I add new packages, but it currently relies on my being careful. >> >> Clearly having very good coverage with tests would help to check the >> health of any new image; I'm slowly working on that. It would be >> nice >> to have ways to check for packaging mistakes. A "smell" that comes >> to >> mind is any methods that I wrote but are not in packages in my load >> script. Is there anything that does such checks? Seaside >> 2.9 includes a tool that helps to manage packages, and _somewhere_ I >> have an image with that loaded and ready for shameless plagairism. >> This seems like such a common task that there must be some good tools >> to handle it?? >> >> Bill >> >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected] >> ] On Behalf Of Stéphane Ducasse >> Sent: Saturday, September 19, 2009 4:07 PM >> To: [email protected] >> Subject: Re: [Pharo-project] Gofer vs Installer >> >>>> >>>> >>>>> goals? >>>> >>>> Perform MC actions (load, update, merge, revert, commit, diff, >>>> recompile) on a set of packages. >>> >>> So, not like Installer that can load packages from everywhere, Gofer >>> will concentrate on MC? What about ScriptLoader? >> >> ScriptLoader will certainly use gofer to install packages instead of >> installer >> >>> Stephane has mentioned Gofer before. Is in the plans to support only >>> MC packages for Pharo and to use Gofer as the tool for load them on >>> pharo. >> >> Yes. >> Because in pharo we do not use anything else besides on changeset to >> kick in the load. >> >>> Or nothing has been decided yet? It is considered? >>>> >>>>> implementation? >>>> >>>> Focus on keeping the system clean, e.g. no empty categories/ >>>> protocols, properly ordered categories/protocols, no duplicated >>>> repositories, etc. >>> >>> Installer can't do that? Is a question, I don't know much about the >>> internals of Installer. >> >> Compared to sometimes ago they were cleaned but >>> >>>> >>>>> speed? >>>> >>>> Not optimized yet. >>>> >>>>> license? >>>> >>>> MIT >>> >>> Can you please give us a big picture of the role Gofer will have? >> >> After discussion at Esug between dale, lukas and me listening :) it >> seems that Metacello will use Gofer to load packages. >> >> Now I think that you should give a try to Gofer and report what is >> missing or not. >> I have some behvaior I would really like to have (that are specific >> to ScriptLoader like tell me which packages have changed since a >> given marked period). >> >> >> >>> >>>> >>>> Lukas >>> >>> Thanks >>> -- >>> Miguel Cobá >>> http://miguel.leugim.com.mx >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [email protected] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
