Re: How best to handle updates for plug-ins?
Re: How best to handle updates for plug-ins?
- Subject: Re: How best to handle updates for plug-ins?
- From: Howard Moon <email@hidden>
- Date: Mon, 16 Jun 2014 08:12:29 -0700
I just now looked at Sparkle, but I don't think that will work. It appears that it checks for updates from WITHIN our software, which we don't want. We want something that runs at system startup (or at specified times), and goes out to our http or ftp site and checks for available updates, downloading and installing them automatically (if desired). While Sparkle says it supports plugins, it is still run from within the plugin, and we can't update the plugin if it's running inside an audio host at the time.
Long ago, I created my own Windows update software for the clients of my transportation-related software - an app that ran in the system tray and checked fro updates. I know that some software still does that kind of thing, both on Mac and Windows. For example, Adobe. The question is, how? And will that kind of approach work in the newer Mac OS versions?
Following that line of thought, how would I create an app (daemon?) that runs at startup and can access the file system and the internet? And how would I install such an app as part of my .mpkg I've created using Packages?
Or is there a better way?
Thanks,
Howard
On Jun 14, 2014, at 12:47 AM, Beatrix Willius <email@hidden> wrote:
> Have you looked at Sparkle? Assuming that you aren’t in the Mac App Store…
>
> On 13.06.2014, at 19:13, Howard Moon <email@hidden> wrote:
>
>> I'm just starting the process of looking into how to provide updates for our audio plug-ins (VST, AudioUnits, AAX), and am looking for advice on where to start. Up until now, users have just had to go to our website to download updates, assuming they know about them. But we want to provide something more automated that will check (or allow checking) if an update is available and allow downloading and installing it without the user having to initiate the process (unless they want to do it manually, naturally).
>>
>> Should we be using the Software Update Service on a dedicated Mac OS X with Server running on it? Or would a custom daemon or something similar installed with our plug-ins and running on the users' systems be more appropriate? We most likely don't want to do the update checks from within our software, because they're plug-ins running inside audio hosts (and may be sandboxed). But I'm just not sure where to begin here. Any help would or pointers on where to begin looking would be appreciated.
>
> Mit freundlichen Grüßen/Regards
>
> Trixi Willius
>
> http://www.mothsoftware.com
> Mail Archiver X: The email archiving solution for professionals
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Installer-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden