Smalltalk › Pharo › Pharo Smalltalk Developers

Why pharo is going over squeaksource when saving code?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

11 messages Options

stepharo

Why pharo is going over squeaksource when saving code?

may be I'm dreaming this morning but when I saved code in the inbox I
saw a query to www.squeaksource.com?

Stef

EstebanLM

Re: Why pharo is going over squeaksource when saving code?

no, is true :(
the configurations for FFI and Alien are pointing to a place there, and since Monticello is… well… not so good… it scans all available repositories to get a version number.
Obviously, not good..
And I think we changed that last year, but obviously is back.

in the mean time, I have in my todo to make a mirror for FFI and Alien in sthub and do a configuration who will take packages from there. That will minimise the problem, but it will still be there :(

Esteban

> On 09 Jan 2016, at 10:07, stepharo <[hidden email]> wrote:
>
> may be I'm dreaming this morning but when I saved code in the inbox I saw a query to www.squeaksource.com?
>
> Stef
>

Sven Van Caekenberghe-2

Re: Why pharo is going over squeaksource when saving code?

In reply to this post by stepharo

I saw that too, I choked in my coffee ;-)

> On 09 Jan 2016, at 10:07, stepharo <[hidden email]> wrote:
>
> may be I'm dreaming this morning but when I saved code in the inbox I saw a query to www.squeaksource.com?
>
> Stef
>

kilon.alios

Re: Why pharo is going over squeaksource when saving code?

eeeehhh that was happening forever at least the last 2 years I am around. How come you guys just noticed ?

On Sat, Jan 9, 2016 at 1:01 PM Sven Van Caekenberghe <[hidden email]> wrote:

I saw that too, I choked in my coffee ;-)

> On 09 Jan 2016, at 10:07, stepharo <[hidden email]> wrote:
>
> may be I'm dreaming this morning but when I saved code in the inbox I saw a query to www.squeaksource.com?
>
> Stef
>

stepharo

Re: Why pharo is going over squeaksource when saving code?

In reply to this post by EstebanLM

thanks esteban. I was surprised.

Le 9/1/16 10:11, Esteban Lorenzano a écrit :

> no, is true :(
> the configurations for FFI and Alien are pointing to a place there, and since Monticello is… well… not so good… it scans all available repositories to get a version number.
> Obviously, not good..
> And I think we changed that last year, but obviously is back.
>
> in the mean time, I have in my todo to make a mirror for FFI and Alien in sthub and do a configuration who will take packages from there. That will minimise the problem, but it will still be there :(
>
> Esteban
>
>> On 09 Jan 2016, at 10:07, stepharo <[hidden email]> wrote:
>>
>> may be I'm dreaming this morning but when I saved code in the inbox I saw a query to www.squeaksource.com?
>>
>> Stef
>>
>

Sven Van Caekenberghe-2

Re: Why pharo is going over squeaksource when saving code?

In reply to this post by kilon.alios

it is a combination of 2 things: the repo must 1st be defined and used by a package, then there is this odd behaviour of checking all repos for version conflicts.

so it depends on what you have loaded.

> On 09 Jan 2016, at 12:34, Dimitris Chloupis <[hidden email]> wrote:
>
> eeeehhh that was happening forever at least the last 2 years I am around. How come you guys just noticed ?
>
> On Sat, Jan 9, 2016 at 1:01 PM Sven Van Caekenberghe <[hidden email]> wrote:
> I saw that too, I choked in my coffee ;-)
>
> > On 09 Jan 2016, at 10:07, stepharo <[hidden email]> wrote:
> >
> > may be I'm dreaming this morning but when I saved code in the inbox I saw a query to www.squeaksource.com?
> >
> > Stef
> >
>
>

stepharo

Re: Why pharo is going over squeaksource when saving code?

In reply to this post by kilon.alios

may be because we are slow :)

Le 9/1/16 12:34, Dimitris Chloupis a écrit :

eeeehhh that was happening forever at least the last 2 years I am around. How come you guys just noticed ?

On Sat, Jan 9, 2016 at 1:01 PM Sven Van Caekenberghe <[hidden email]> wrote:

I saw that too, I choked in my coffee ;-)

> On 09 Jan 2016, at 10:07, stepharo <[hidden email]> wrote:
>
> may be I'm dreaming this morning but when I saved code in the inbox I saw a query to www.squeaksource.com?
>
> Stef
>

kilon.alios

Re: Why pharo is going over squeaksource when saving code?

In reply to this post by Sven Van Caekenberghe-2

why it has to check for version conflicts ? once I tell pharo to install a package thats what I want it to do. Is this practice really necessary ?

On Sat, Jan 9, 2016 at 2:58 PM Sven Van Caekenberghe <[hidden email]> wrote:

it is a combination of 2 things: the repo must 1st be defined and used by a package, then there is this odd behaviour of checking all repos for version conflicts.

so it depends on what you have loaded.

> On 09 Jan 2016, at 12:34, Dimitris Chloupis <[hidden email]> wrote:
>
> eeeehhh that was happening forever at least the last 2 years I am around. How come you guys just noticed ?
>
> On Sat, Jan 9, 2016 at 1:01 PM Sven Van Caekenberghe <[hidden email]> wrote:
> I saw that too, I choked in my coffee ;-)
>
> > On 09 Jan 2016, at 10:07, stepharo <[hidden email]> wrote:
> >
> > may be I'm dreaming this morning but when I saved code in the inbox I saw a query to www.squeaksource.com?
> >
> > Stef
> >
>
>

kilon.alios

Re: Why pharo is going over squeaksource when saving code?

Slow is definetly not what your are, neither stupid because pharo will not be in a state that it is and neither slow to implement things because pharo would not be so rapidly moving forward as it is. But then by using smalltalk you basically cheat , but thats our common secret ,no need to get out of this community ;)

On Sat, Jan 9, 2016 at 3:04 PM Dimitris Chloupis <[hidden email]> wrote:

why it has to check for version conflicts ? once I tell pharo to install a package thats what I want it to do. Is this practice really necessary ?

On Sat, Jan 9, 2016 at 2:58 PM Sven Van Caekenberghe <[hidden email]> wrote:
it is a combination of 2 things: the repo must 1st be defined and used by a package, then there is this odd behaviour of checking all repos for version conflicts.

so it depends on what you have loaded.

> On 09 Jan 2016, at 12:34, Dimitris Chloupis <[hidden email]> wrote:
>
> eeeehhh that was happening forever at least the last 2 years I am around. How come you guys just noticed ?
>
> On Sat, Jan 9, 2016 at 1:01 PM Sven Van Caekenberghe <[hidden email]> wrote:
> I saw that too, I choked in my coffee ;-)
>
> > On 09 Jan 2016, at 10:07, stepharo <[hidden email]> wrote:
> >
> > may be I'm dreaming this morning but when I saved code in the inbox I saw a query to www.squeaksource.com?
> >
> > Stef
> >
>
>

Thierry Goubier

Re: Why pharo is going over squeaksource when saving code?

In reply to this post by kilon.alios

Le 9 janv. 2016 2:06 PM, "Dimitris Chloupis" <[hidden email]> a écrit :
>
> why it has to check for version conflicts ? once I tell pharo to install a package thats what I want it to do. Is this practice really necessary ?

This is because Monticello needs to check all repositories to choose a version number higher by one to all version numbers of that package in all repositories.

Of course, this could fail if you don't check all mc repositories in the whole world...

Of course, this has no meaning for gitfiletree repositories...

Thierry

> On Sat, Jan 9, 2016 at 2:58 PM Sven Van Caekenberghe <[hidden email]> wrote:
>>
>> it is a combination of 2 things: the repo must 1st be defined and used by a package, then there is this odd behaviour of checking all repos for version conflicts.
>>
>> so it depends on what you have loaded.
>>
>> > On 09 Jan 2016, at 12:34, Dimitris Chloupis <[hidden email]> wrote:
>> >
>> > eeeehhh that was happening forever at least the last 2 years I am around. How come you guys just noticed ?
>> >
>> > On Sat, Jan 9, 2016 at 1:01 PM Sven Van Caekenberghe <[hidden email]> wrote:
>> > I saw that too, I choked in my coffee ;-)
>> >
>> > > On 09 Jan 2016, at 10:07, stepharo <[hidden email]> wrote:
>> > >
>> > > may be I'm dreaming this morning but when I saved code in the inbox I saw a query to www.squeaksource.com?
>> > >
>> > > Stef
>> > >
>> >
>> >
>>
>>

stepharo

Re: Why pharo is going over squeaksource when saving code?

I know.
What I meant is why do we have still all the repositories hanging around. They slow us down.

Stef

Le 9/1/16 14:42, Thierry Goubier a écrit :

Le 9 janv. 2016 2:06 PM, "Dimitris Chloupis" <[hidden email]> a écrit :
>
> why it has to check for version conflicts ? once I tell pharo to install a package thats what I want it to do. Is this practice really necessary ?

This is because Monticello needs to check all repositories to choose a version number higher by one to all version numbers of that package in all repositories.

Of course, this could fail if you don't check all mc repositories in the whole world...

Of course, this has no meaning for gitfiletree repositories...

Thierry

> On Sat, Jan 9, 2016 at 2:58 PM Sven Van Caekenberghe <[hidden email]> wrote:
>>
>> it is a combination of 2 things: the repo must 1st be defined and used by a package, then there is this odd behaviour of checking all repos for version conflicts.
>>
>> so it depends on what you have loaded.
>>
>> > On 09 Jan 2016, at 12:34, Dimitris Chloupis <[hidden email]> wrote:
>> >
>> > eeeehhh that was happening forever at least the last 2 years I am around. How come you guys just noticed ?
>> >
>> > On Sat, Jan 9, 2016 at 1:01 PM Sven Van Caekenberghe <[hidden email]> wrote:
>> > I saw that too, I choked in my coffee ;-)
>> >
>> > > On 09 Jan 2016, at 10:07, stepharo <[hidden email]> wrote:
>> > >
>> > > may be I'm dreaming this morning but when I saved code in the inbox I saw a query to www.squeaksource.com?
>> > >
>> > > Stef
>> > >
>> >
>> >
>>
>>