Isn't this the sort of thing which you can pre-emptively fix using the developer's release of each point update? Shouldn't those releases contain the new version of mail, along with the updated UUIDs?
On Nov 10, 12:17 am, Mike <[email protected]> wrote: > The reason for Mail plugins breaking so often in Snow Leopard is this: > In Mail 4.0 or higher (Snow Leopard starts at 4.0) is started, it > scans all plugins for compatibility information. If it detects a > plugin from an older version of Mail (in this case, a plugin for 4.1 > trying to run in 4.2) it is automatically disables the plugin, even if > it works just fine. Each plugin must explicitly tell Mail that the > plugin is made for that EXACT version of Mail. So every time Mail is > updated, all Mail plugins must be updated as well to explicitly state > that they work with the new version of Mail. > > Yes, I know, that's dumb. But that's the way it is and we're stuck > with it. A quick change to the GrowlMail plugin to tell Mail that it > is compatible is all that's needed unless more problems or > incompatibilities arise after that (not that we'd be able to find the > problems before the compatibility update because the plugin won't run > in Mail 4.2, so we can't bugtest). It's a backwards way of doing > things. An update can be done for GrowlMail tonight and work just fine. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=.
