On Feb 24, 2009, at 7:26 PM, Michael Rueger wrote:
Michael Rueger wrote:
Stéphane Ducasse wrote:
Ok I will have a look. I was probably silly
Well, basically the Kom package is in the old Squeak tradition of mangling the system until it seems fit. The number and kind of extensions all over the system make it more or less incompatible with the MIME (and other) changes in the current Pharo image.
This is a situation we will increasingly encounter when we start to really deliver on the promise of cleaning up the system: packages will become incompatible to an extent that we can't -and shouldn't or rather must not- patch around.
Probably now for resetMIMEdatabase it was not an extension of anypackage in Squeak 3.9. So can you fix that or there is something I do not understand. Then I think that we should first make sure that seaside can run and after we should really put pression on the KOM maintainer or declare that it is incompatible with pharo and hope that
Polymorph is the next candidate regarding the unicode changes as it touches the same areas of the system.
Comments?
We discussed the overriding policy of Polymorph with adrian lukas and marcus and normally if I remember well we should contact gary to get a much better integration. We really think that this is important to not have override in Pharo. May be gary will read this one else we should launch a new thread. Stef