[squeak-dev] Packages, Packages, Packages

Igor Stasenko siguctua at gmail.com
Sat Dec 12 18:28:05 UTC 2009

2009/12/12 Jecel Assumpcao Jr <jecel at merlintec.com>:
> Andreas Raab wrote:
>> I think that's all the serious contenders at this point (if I'm missing
>> something please let me know). From my perspective, I don't care which
>> solution we choose as long as it fits the bill of:
>> * Being indexable by Google
>> * Reasonable dependency management
> My experience with RPMs, RPMs+Synaptic, APT, Portage and many others is
> that reasonable dependency management is sometimes unreasonable. When
> that happens, what will save you is if "being indexable by Google" means
> the capability to find out which package has a particular file. In our
> case, what we need badly right now is, given the name of some missing
> class, figure out what to load into our image to fix that.

+100. We need just a simple web server which can give us the plain
simple answer - the list of packages which including class with given
This is all what i need most of the times (when loading stuff using
MC), because i can easily solve the rest using existing tools.
So if we could have it, the need of having & developing/adopting
highly advanced dependency management tools will be not an issue.
Keep it simply stupid.

Moreover, by having such global registry, where people could register
their packages, we also can deal with another issue: class names
clashing. Developer, before publishing the package could simply check
if given class is already used by someone else, and choose another

> Of course, given the kinds of names that Squeak packages tend to have,
> "being indexable by Google" also helps if it means being able to type
> "squeak multiple windows" and have the first hit be "Areithfa Ffenestri"
> http://wiki.squeak.org/squeak/3862
> -- Jecel

Best regards,
Igor Stasenko AKA sig.

More information about the Squeak-dev mailing list