external package handling ... a concrete case

Hi guys

I'm cleaning nautilus model and Spotter is extended.
Now I will not publish the fix in Spotter, I will not update a
configuration of a tool I do not know.
So what should I do, stop working? No this is not possible. So I will
push this changes in the inbox and
integrate it and GT people should merge the fix in their baseline when
they want.
Or I will really stop doing anything for Pharo 50 alpha.

Stef

spotterActDefault
     ^ Nautilus openOnPackage: self

but that happens because GTools guys made a mistake:

spotterActDefault
        ^ Smalltalk tools browser openOnPackage: self

that’s the correct implementation of that method.

Esteban

Le 6/5/15 22:37, Esteban Lorenzano a écrit :
> but that happens because GTools guys made a mistake:
>
> spotterActDefault
> ^ Smalltalk tools browser openOnPackage: self
>
> that’s the correct implementation of that method.

Ok but I do not care. This is just an example of the problem.
I will **not** publish the GTSpotter code nor update the configuration
because I do know the internal of GT.
If I would be maintaining an external pharo tool I would hate that
somebody publish random code to it.

When we publish a change in Pharo for external tools this is like a pull
request!

Stef

I will

In the meantime can you let us know when you integrate a slice for a project managed through configurations.

I cannot guess when this happens.

On Wed, May 6, 2015 at 11:24 PM, stepharo <[hidden email]> wrote:

Le 6/5/15 22:37, Esteban Lorenzano a écrit :

but that happens because GTools guys made a mistake:

spotterActDefault
        ^ Smalltalk tools browser openOnPackage: self

that’s the correct implementation of that method.

Ok but I do not care. This is just an example of the problem.
I will **not** publish the GTSpotter code nor update the configuration because I do know the internal of GT.
If I would be maintaining an external pharo tool I would hate that somebody publish random code to it.

The configuration of spotter and of any other project from gt is nothing special nor complicated.

Feel free to update it or push changes directly to the repo at any time.

You'll get no complaints from us :)

Cheers,

Andrei

 

When we publish a change in Pharo for external tools this is like a pull request!

Stef

Esteban

On 06 May 2015, at 22:14, stepharo <[hidden email]> wrote:

Hi guys

I'm cleaning nautilus model and Spotter is extended.
Now I will not publish the fix in Spotter, I will not update a configuration of a tool I do not know.
So what should I do, stop working? No this is not possible. So I will push this changes in the inbox and
integrate it and GT people should merge the fix in their baseline when they want.
Or I will really stop doing anything for Pharo 50 alpha.

Stef

spotterActDefault
    ^ Nautilus openOnPackage: self