Thanks Torsten.
Indeed, renaming the package solved the problem.
On Thu, Jan 29, 2015 at 12:11 AM, Torsten Bergmann wrote:
> Because "MyPackage" and "MyPackage-Ext" fall into the same
> class categories. The name "MyPackage" is part of the string
> "MyPackage-Ext".
>
> Packages and class categor
Because "MyPackage" and "MyPackage-Ext" fall into the same
class categories. The name "MyPackage" is part of the string
"MyPackage-Ext".
Packages and class categories are mixed to provide Pharo packages
and with this you are also still able to use old code or
import code from other Smalltalks.
Esteban,
I tried your script in my image. I did not help i.e. dirty packages are
still present in Monticello browser ( and I still do not know why).
On Wed, Jan 28, 2015 at 5:05 PM, Esteban Lorenzano
wrote:
> You can try rebuilding the rpackage structure.
>
> 1) close all browsers
> 2) execute
You can try rebuilding the rpackage structure.
1) close all browsers
2) execute RPackageOrganizer default initializeFromMC
Esteban
> On 28 Jan 2015, at 16:50, Usman Bhatti wrote:
>
> Hello,
>
> I have two packages MyPackage and MyPackage-Ext. When I load MyPackge-Ext,
> MyPackage becomes di
Hello,
I have two packages MyPackage and MyPackage-Ext. When I load MyPackge-Ext,
MyPackage becomes dirty and do not have any clue why. When I try to see
changes in MyPackage in Monticello Browser, the package becomes clean again.
There are two possibilities why MyPackage-Ext makes MyPackage dirt
