Re: Conditionally destination for package
Re: Conditionally destination for package
- Subject: Re: Conditionally destination for package
- From: Matthias Schroeder <email@hidden>
- Date: Fri, 21 Mar 2014 11:44:41 +0100
Hi,
On 03/19/2014 12:37 AM, Stephane Sudre wrote:
...
Basically the idea here is to avoid a copy or a move from the post
install script.
That brings up another question: is there a way that I can avoid this
copy or move when I repackage something? My use case is the following:
We have Product A, already in form of a package or an Installer app. We
want to add Product B (and sometimes product C), also in form of a package.
What I currently do is to create a distribution package that has
packages A,B and C as payload, and run the command line installer on the
delivered payload.
For small packages this is no big issue, but for larger packages the
re-shuffling of the data costs a lot of time. Is there a more economic
way to tell Packages
if requirementA then install packageA
if requirementB then install packageB
if requirementC then install packageC
Matthias
_______________________________________________
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