[Sparkle] Avoiding an incompatible update

[Mark Munz]

You could maybe do an update to the older product, so that it looked
at a different URL based on the OS it was running on.

I do this for beta users. If a flag is set to check for beta releases,
I have Sparkle use a different URL than for non-beta users. When I
want both users to get the update (ie. final releases, I post the
update to both URLs).

Mark

On 1/20/08, David Dunham <dunham at mac.com> wrote:
> I'm planning a Leopard-only update, and realized that I don't have
> anything in place to prevent a user running Tiger from updating to
> this version. How are people handling this?
>
> One thought that crossed my mind was to switch the URL that Sparkle
> uses. This would allow the Leopard only version to have Sparkle
> updates. And it would keep Tiger users safe. But it would prevent
> Leopard users from learning about the update.
>
> David Dunham           A Sharp, LLC           +1 206 783 7404
> The Opal outliner is now available!  http://a-sharp.com/opal/
>
> _______________________________________________
> Sparkle mailing list
> Sparkle at lists.andymatuschak.org
> http://lists.andymatuschak.org/listinfo.cgi/sparkle-andymatuschak.org
>


-- 
Mark Munz
unmarked software
http://www.unmarked.com/