package management and classes are orthogonal: you can have a class in the system outside the package structure. so yes.. removing a class from system will certainly remove them from package structure… but not the opposite: unregistering a package is just that: unregistering a package (the classes will remain). rpackage api needs to be revisited (yet once again) un pharo4… but for now, is like that :) Esteban On 18 Mar 2014, at 18:34, Ben Coman <btc@openinworld.com> wrote:

RPackageOrganizer has protocol 'public registration' with methods: #registerPackageNamed: and #unregisterPackageNamed:

So I presume I am free to evaluate the following as separate steps)...

1. RPackageOrganizer default registerPackageNamed: 'MyTest'. "-->package is created okay"

2. Object subclass: #MyTestClass instanceVariableNames: '' classVariableNames: '' category: 'MyTest'. "-->class is created okay"

3. RPackageOrganizer default unregisterPackageNamed: 'MyTest'. "-->package disappears okay"

4. RPackageOrganizer default registerPackageNamed: 'MyTest'. "-->package created okay"

5. Object subclass: #MyTestClass instanceVariableNames: '' classVariableNames: '' category: 'MyTest'. "-->class does not appear"

However if I go... 6a. Smalltalk removeKey: #MyTestClass .

6b. Object subclass: #MyTestClass instanceVariableNames: '' classVariableNames: '' category: 'MyTest'.

"-->then the class does appear"

Should I need to be cleaning up manually per step 6a?

cheers -ben