Definitively not well woken up yet :) > from > source.lukasrenggli.com/flair > > I'm about to write a chapter on it for PharoByexample2 > > Stef > > > On Sep 20, 2009, at 8:30 AM, Schwab,Wilhelm K wrote: > >> Sounds great! Is it downloadable? >> >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected] >> ] On Behalf Of Lukas Renggli >> Sent: Sunday, September 20, 2009 1:18 AM >> To: [email protected] >> Subject: Re: [Pharo-project] Gofer vs Installer >> >>> 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?? >> >> That's exactly Gofer. Seaside 3 is one of the reasons why I wrote it. >> >> Lukas >> >>> >>> 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 >>> >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> 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
