On Wed, Nov 10, 2010 at 5:42 PM, Peter Hosey <[email protected]> wrote: > On Nov 10, 2010, at 15:35:31, Richard L. Hamilton wrote: >> New UUIDs for 10.6.5: >> in /Applications/Mail.app/Contents/Info.plist >> <string>BDD81F4D-6881-4A8D-94A7-E67410089EEB</string> >> in /System/Library/Frameworks/Message.framework/Resources/Info.plist >> <string>857A142A-AB81-4D99-BECC-D1B55A86D94E</string> >> >> Working ok so far after adding those... > > Remember, folks: > > 1. It's a lot easier to just uninstall GrowlMail and wait for us to release a > new version than to try to hack your GrowlMail into working. > 2. There's always the possibility of some conflict between GrowlMail 1.2.1 > and 10.6.5 that could cause data loss. We haven't tested this yet. If you > hack your GrowlMail to make it work, you accept that risk. > > If you go through with it, please let us know whether it works or doesn't. >
Is the uuid updater in a releaseable state? If not how long would it take to get there? Essentially the requirements are to launch it, click a button, provide a warning which is effectively what you say here, and then update the UUID and move the growlmail bundle back to the enabled, and then tell the end user they need to restart mail. Chris -- 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=en.
