renamed app won't install

Unfortunately, you're out of luck there: since your users already have the older version (which *is* case sensitive) installed, and that's the version which would be performing the relevant checks, you can't make any change to your newer version that would make this behavior possible.

One (unfortunate) possibility would be for you to ship the update to your app with the old name, then have the app rename itself on first launch if appropriate.

Yes - I thought it wouldn't work but was trying to think of a way to rename - maybe not a big deal to implement though a little scary...

Thanks Andy as always for your great Sparkle.

best, Rob

On Sep 27, 2011, at 1:25 PM, Andy Matuschak wrote:

> Your question #172281 on Sparkle changed:
> https://answers.launchpad.net/sparkle/+question/172281
>
> Status: Open => Answered
>
> Andy Matuschak proposed the following answer:
> Unfortunately, you're out of luck there: since your users already have
> the older version (which *is* case sensitive) installed, and that's the
> version which would be performing the relevant checks, you can't make
> any change to your newer version that would make this behavior possible.
>
> One (unfortunate) possibility would be for you to ship the update to
> your app with the old name, then have the app rename itself on first
> launch if appropriate.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/sparkle/+question/172281/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/sparkle/+question/172281
>
> You received this question notification because you asked the question.

Perhaps what you could do is introduce an intermediate update that will use the old name and will be updated through the old name, but contains a modified Sparkle bundle that checks the name case insensitively. This intermediate update should then look for a different feed URL, which will contain the future updates with the different name. This way all old (and the current) versions will use the old feed URL and eventually end up with this intermediate update, while the intermediate and later updates will use a different feed that links to updates with the new name.

Well, I thought of that but again I need to modify the Sparkle bundle for the intermediary so it can move to the new version with the case sensitive name. I am happy to modify the bundle but can I? I don't have the source code or know if Andy makes that available.

Cheers, Rob

Sparkle is open-source and licensed without encumbrance. http://github.com/andymatuschak/Sparkle/

And moreover the distribution contains all the source code.

I think I will go with Andy's (unfortunate) suggestion to change the app name on first launch for the intermediary update.

I ran into a lot of errors trying to build the Sparkle source:

[NSString stringWithFormat:SULocalizedString(@"Updating %@", nil), [host name]];

error: format not a string literal….. it doesn't seem to be picking up the #define for SULocalizedString

I may tinker some more but I found that the rename() function can rename the app while running which is not too scary .

Thanks, rob