First, thanks for feedback.
Now I should be the Mantis coordinator and we have now a 5.2 project for
made bug reports.
I send another mail asking for how to have a easy mail send from inside
Squeak.
Take my ail about soundsEnabled as proof of collecting info for made a
Mantis report.
The error comes from importing my old SmartTrashMorph, a long time ago when
you throw some morph on Trash a sound is produced.

SoundService soundEnabled is which we have now , so no bug only need change
old code


On 16/08/2018, 09:51, "Nicolas Cellier" <nicolas.cellier.aka.nice at gmail.com>
wrote:

> Hi Edgar,
> First, I see no such sender of #soundsEnabled in base image, so it's more a
> problem of uncompatibility with add-on packages (extensions) than a problem of
> base image, right?
> 
> Then, thanks to commit messages in the mailing list, I can trace that
> Preferences class>>#soundsEnabled - which is a EToys thing - was added in
> Trunk: System-tfel.902.mcz (which itself is a merge with System-tfel.882).
> 
> But unfortunately, I can't easily trace when this message was removed in
> favour of a doesNotUnderstand: solution...
> Maybe it was removed at a time when the mailing list reports were not
> functional?
> Or maybe, the changes were not reported because too long...
> (That's a bad feature IMO, on the assumption that code should never be too
> long, we should not need any such guard anyway...).
> 
> The thing to do before/after loading such EToys like extension is to perform
> Etoys like initialization, and that could well be a responsibility of
> extension code, rather than of base image. So maybe it's not a problem of
> Trunk by itself...
> The question is how do we advertize the package maintainers about these new
> responsibilities caused by evolutions of Trunk (understand evolution as
> shrinking/simplifying)?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180816/7713a7d0/attachment-0001.html>