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 <[email protected]> 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 <[email protected]>
> 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 <[email protected]>
> wrote:
> > I saw that too, I choked in my coffee ;-)
> >
> > > On 09 Jan 2016, at 10:07, stepharo <[email protected]> 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
> > >
> >
> >
>
>
>

Reply via email to