On 27 Nov 2015, at 13:32, Dimitris Chloupis <kilon.alios@gmail.com> wrote:
Marcus you are awesome thank, so all I had to do was erase my Ephestos.changes file and now I can browse addMiscExtraTo: and I have no MNUs or red boxes of doom.
There was something fishy about my changes file, I found addMiscExtraTo: in PharoV4.sources and in Ephestos.changes, the issue is that I never touched that method , so why should it be in changes file ? I thought changes are for the things you change in the image.
But no complains , it looks like now the problem is gone.
The .changes does not only have the changes that you did, but in addition all changes that we did to Pharo since the release of Pharo4⦠The whole mechanism is not very good⦠we really should replace it. The good news is that we are working on the first step already: Epicea will be used for recording changes, so after that we re free to simplify source storage as it will now overlap anymore with change history recording. Be careful with an image where you delete the .changes: all methods that point to that file will be decompiled⦠losing comments and much more. The best thing is to re-create an image from the release (loading your code). Marcus