Hi Brad,

Brad Fuller wrote:

> What you _really_ do when you add a Package is add a Category, 
> right?   Categories are arbitrary. If you add VMMaker-Plugins you get 
> all of the classes in the category, right? I just want to save my one 
> class from that category, I don't want to save all of them. What am I 
> missing?

I think that what you are missing is a little of context. Very long 
before Monticello existed, Squeak package management was centered on 
class categories. On that time, developers  by convention used the class 
categories as if they where packages. So you didn't create packages. 
What you did was to create class categories and put the classes on there 
and file-in and out the entire categories.

Later, when DVS came to life (DVS is Monticello's ancestor), Avi and 
Julian (the creators of DVS and Monticello) decided that for packages 
they were gonna use the same concept that historically was being used 
for Packages on Squeak, the class categories.

Now. Answering to your question. You can't make that a class that 
belongs to another class category be part of your package. That class 
only belongs to the package where it is defined. If you have a package 
that depends on that class then your package depends on the other class' 
package as well, and you can't escape to that.

One thing that you might be able to do is to move out the classes that 
you are interested in into a new package,  and make the other 2 
dependants of the new one. (like class refactorings).

Regards,
Hernán