Re: Installing in multiple locations
Re: Installing in multiple locations
- Subject: Re: Installing in multiple locations
- From: Andrew Keller <email@hidden>
- Date: Mon, 25 Feb 2013 07:54:57 -0500
On Feb 25, 2013, at 6:08 AM, Wojciech Toman wrote:
> I'm fairly new to PackageMaker and would therefore like to hear your
> suggestions how to approach a following task. I need to install
> exactly same contents to several different locations. Contents is a
> plugin and locations are host applications. I tried using choices
> (each with the same contents) for that but it seems that each choice
> increases size of the installer. Of course I would prefer to reuse the
> contents instead of duplicating it inside the installer.
>
> So there must be a better way of doing this.
First, PackageMaker was deprecated years ago. It's not a good idea to use it for new projects.
Second, duplicates of anything introduce another level of complexity in any system. It's more things to maintain, and more things that can break. Can you refactor your architecture to not use duplicates?
Third, the compression technique used by installer packages is not smart enough to detect duplicates, in my experience. One possible alternative would be to install the component into a single location, and use a postinstall script to copy it to other locations.
HTH
Andrew Keller
_______________________________________________
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