El sáb, 19-09-2009 a las 18:34 +0200, Lukas Renggli escribió: > For Gofer: > > > 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? 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. 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. > > > speed? > > Not optimized yet. > > > license? > > MIT Can you please give us a big picture of the role Gofer will have? > > 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
