Adrian Lienhard wrote:
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
Half of what you describe is in Sake/Packages Keith