Re: Packages vs. other package creator software
Re: Packages vs. other package creator software
- Subject: Re: Packages vs. other package creator software
- From: Stephen Kay <email@hidden>
- Date: Sun, 26 Feb 2017 20:28:54 -0700
- Thread-topic: Packages vs. other package creator software
On 2/25/17 11:19 PM, "Motti Shneor" <email@hidden> wrote:
>Packages is wonderful. I used it for a rather complicated
>installation/deployment task, and It made it easy.
That's good to know!
>One thing though. You say you want to distribute a Mac Application? If so
>- there is no need for an installer. If you just upgrade your app a
>little (to not spread its stuff everywhere, but rather store its
>resources in its own App bundle) you can skip the ³Installer² thing
>altogether. That¹s also Apple¹s recommendation.
I've pretty much done that with everything that I can.
>You should only make an installer if you have special things to put in
>special places, and even then - other methods are preferable.
Well, I do have "special things" that need to be put in special places,
i.e. drivers, support files for /Library/Application Support/ etc. What
other methods are you referring to?
>
>Another point - You cannot deploy an app that needs an installer in
>Apple¹s Mac App store. The deployment process takes an App archive - not
>an installation package. Rather, the App-store itself creates a temporary
>installer package from your app when deploying it to users.
Never used the app store (so far), and don't envision doing so with this
app. Given how old it is and carbon-based, from what I understand it would
never be able to satisfy Apple's requirements for apps these days. But if
I ever come up with a newer app...good to know.
Thanks,
- Stephen
_______________________________________________
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