Yes, this was like that since ever.
For Pharo3 I added a workaround: after every build, on the CI server I removed
all repos and added the default repos.
This of course deleted all the repos defined for the “externallly” managed
projects, so
we just removed this cleanup in Pharo4, bringing back the mess that we had
before.
We need to fix this.
Marcus
> On 30 May 2015, at 17:39, Ben Coman <[email protected]> wrote:
>
> This has been for a while, even in Pharo 4 I think. I *assumed* it was by
> design and I was just learning to live with it.
> cheers -ben
>
> On Sat, May 30, 2015 at 6:07 PM, Esteban Lorenzano <[email protected]
> <mailto:[email protected]>> wrote:
> Hi,
>
> I’m having a lot of problems with monticello lately.
> And it is not just the change of MCLazyVersionInfo (that affects just the
> history).
>
> Now, looks like packages are keeping their own private list of repositories.
> Look at the example:
>
>
>
> <Screen Shot 2015-05-30 at 12.04.49.png>
>
> Notice the “All” selection. Now see with “Package” selected:
>
> <Screen Shot 2015-05-30 at 12.05.38.png>
>
> And it is breaking not just my nerves, but a lot of tools, etc.
>
> So, I don’t know it this was on purpose to avoid repositories pollution… but
> this is a bug or a bad change :)
>
> Can you confirm the problem?
>
> Esteban
>
