Smalltalk › Pharo › Pharo Smalltalk Users

dirty packages

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Usman Bhatti

dirty packages

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 dirty:

-> There are names conflict of some sort (MyPackage-Ext can be seen as a category for MyPackage).

-> Overriding of the extension methods introduced on the third package. Now I wrote a small script to verify it:

firstCollection := (RPackage organizer packageNamed: 'MyPackage') extensionMethods values flatten.

secondCollection := (RPackage organizer packageNamed: 'MyPackage-Ext') extensionMethods values flatten.

(secondCollection intersection: firstCollection)

The above script gives empty result so there are no overriding selectors.

Any ideas how can I hack into Monticello to see what is causing MyPackage to become dirty while I load the second one manually. May be by logging the override load definitions on Transcript?

In general, will it be possible to see overriding without these disappearing when doing changes on a dirty package?

tx in advance.

Usman

EstebanLM

Re: dirty packages

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 <[hidden email]> wrote:
>
> 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 dirty:
> -> There are names conflict of some sort (MyPackage-Ext can be seen as a category for MyPackage).
> -> Overriding of the extension methods introduced on the third package. Now I wrote a small script to verify it:
> firstCollection := (RPackage organizer packageNamed: 'MyPackage') extensionMethods values flatten.
> secondCollection := (RPackage organizer packageNamed: 'MyPackage-Ext') extensionMethods values flatten.
> (secondCollection intersection: firstCollection)
> The above script gives empty result so there are no overriding selectors.
>
> Any ideas how can I hack into Monticello to see what is causing MyPackage to become dirty while I load the second one manually. May be by logging the override load definitions on Transcript?
>
> In general, will it be possible to see overriding without these disappearing when doing changes on a dirty package?
>
>
> tx in advance.
>
> Usman
>
>

Usman Bhatti

Re: dirty packages

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 <[hidden email]> wrote:

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 <[hidden email]> wrote:
>
> 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 dirty:
> -> There are names conflict of some sort (MyPackage-Ext can be seen as a category for MyPackage).
> -> Overriding of the extension methods introduced on the third package. Now I wrote a small script to verify it:
> firstCollection := (RPackage organizer packageNamed: 'MyPackage') extensionMethods values flatten.
> secondCollection := (RPackage organizer packageNamed: 'MyPackage-Ext') extensionMethods values flatten.
> (secondCollection intersection: firstCollection)
> The above script gives empty result so there are no overriding selectors.
>
> Any ideas how can I hack into Monticello to see what is causing MyPackage to become dirty while I load the second one manually. May be by logging the override load definitions on Transcript?
>
> In general, will it be possible to see overriding without these disappearing when doing changes on a dirty package?
>
>
> tx in advance.
>
> Usman
>
>