>> >> >>> 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
