Hi, I really think we need a package management system and a process to maintain it. The goal is that loading and using non-core packages "just works" (unlike for instance SqueakMap, where loading more often fails than succeeds because there are a lot of obsolete packages and a dependency mechanism is missing). - There should be a responsible maintainer for each package - For each package there should be a known way to discuss and report problems - A gate keeper includes and removes packages from the set depending on their status This limits the set of included packages (at least initially) but would increase the quality and hence the user experience. Maybe there could be two sets, a stable and an unstable set. New packages would first go to the unstable set and then move up to the stable set after a while. An automated build process could load packages into new builds and report the result of the tests. The package management system does not need to be very sophisticated, but it should manage dependencies and have a simple GUI (to search for packages and see what is already loaded). Cheers, Adrian On Aug 8, 2009, at 12:31 , Stéphane Ducasse wrote:
Hi
in the future I would like to have a process like that to maintain package like sound (or morphic extras) or any package that are not core else we will not be able to maintain them or to apply package wide changes.
- we mark the packages that are not in the image but that we want to maintain - at integration step we load all the external packages - integrate - publish in different repos
Else I bet that we will not be able to maintain the non core packages.
Stef
PS: I'm integrating
Issue 1051: Cuis 0053-ensure-close.1.cs and some changes touched sound so this is good experiment.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project