Conversation
|
This seems like a good idea to me. Can we use |
|
OK, I was wrong about |
|
Autoupdate.app doesn't have its own strings files. I'd rather not split them, as this makes strings maintenance harder. |
|
OK, SUUpdater seems like a better fit for the bundle |
|
What are all the .strings files I see generated inside of Autoupdate.app for? I see that some of the resource files are copied over from Sparkle.framework to Autoupdate.app perhaps maybe to avoid this problem If you grep for |
Oh, I didn't notice there were there. It's a dupe of framework's strings files, so hopefully it could be avoided? Seems wasteful.
That class is currently independent of SUUpdater, and that call works, so I'd leave it as is. |
Don’t keep important settings in Sparkle’s Info.plist
It may seem 'wasteful' but could help save us from this issue, which I think would be worth it. |
|
If it's too wasteful to have two copies, you can put only one copy in Autoupdate and have a relative symlink in the framework that points to the file in Autoupdate. |
Re #573