Re: Option to execute a command?
Re: Option to execute a command?
- Subject: Re: Option to execute a command?
- From: Nathan Sims <email@hidden>
- Date: Tue, 29 Mar 2011 15:32:48 -0700
No, this approach doesn't work. There's no telling when the script gets invoked.
Surely PackageMaker can do something as simple as run a pre- and post- flight script??
On Mar 29, 2011, at 12:46 PM, Nathan Sims wrote:
> Interesting! If I do this, it prompts me with the path of the script. Does PM automatically include this script in the package, or does it assume it preexists on the machine you're installing on?
>
>
> On Mar 29, 2011, at 12:30 PM, Allister Banks wrote:
>
>> Requirements tab -> add -> If/Result of Script -> file path to your script?
>>
>> Allister
>>
>> On Mar 29, 2011, at 3:10 PM, Nathan Sims wrote:
>>
>>> Sounds fine, but how do I tell PackageMaker to do that?
>>>
>>> On Mar 29, 2011, at 12:01 PM, Allister Banks wrote:
>>>
>>>> Hey Mr. Sims,
>>>>
>>>> What if you run a script that has your commands in it as part of that preinstall?
>>>>
>>>> Allister
>> _______________________________________________
>> 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
_______________________________________________
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