Squeak
  links to this page:    
View this PageEdit this PageUploads to this PageHistory of this PageTop of the SwikiRecent ChangesSearch the SwikiHelp Guide
Summary: Package Universes
Last updated at 10:00 pm UTC on 1 March 2005
Reported by Lex Spoon

What problems are being addressed

  1. Easy installation of packages written by other Squeakers, with reasonable likelihood that what you see will work in your current image. ("Gee, I'd like a regular expressions package, let me grab one.")
  2. Developing stable sets of packages, to go along with stable releases. ("Our software is the center of the business; we'd like stable packages, please, even if they are old.")

How it solves the problem

The approach is that every Squeak image lives within one "package universe". The image can only see packages that are available in that universe. If a developer uses that image publishes a package, it is only seen by other images that are in the same universe. Each universe has its own policies about what changes are allowed. By having different policies, one can support wild and crazy development in one universe, while squeezing out the bugs (at the expense of gaining new features) in another universe.

Useful links

Package Universes

For coherence I think the author should write the sections above this line.
People can add what they want to these later sections, and can suggest that the author change the rest.

What's cool about it

  1. Simple dependencies work. It's enough to say things like "Scamper needs Network-HTML".
  2. Local, non-public package repositories are supported. Work groups can collaborate with each other without needing to publish all of their packages to the world. This might be called Privacy in the Infrastructure.
  3. Package names can be shorter, e.g. "Refactoring Browser" instead of "Refactoring Browser for 3.7".
  4. Likewise, package descriptions can be targeted to users in the current universe. There is no need for "if you are in a 3.5 image, then blah, but if you are in 3.8, then blarg".

What's not

  1. Package information is entered from scratch; it would be better to re-use information from the package instead of making developers type it all in again.
  2. The accounts management, used for posting new packages, is primitive and is separate from all the million other accounts management systems we have at this point (e.g., SqueakMap, SqueakPeople, SqueakSource).

Commentary




Back to New Modules