February 2009 - Installer-dev

Re: What do "Start xyz" options for "On Failure" do?
by Paul Cook 26 Feb '09

26 Feb '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Again, thanks very much for your help. No, I didn't temper with them. Anyway, Is the following what you had in mind? Best Wishes, Paul On Feb 24, 2009, at 10:33 PM, Stephane Sudre wrote: The code generated by PackageMaker is incorrect if the package has not been tampered with after build. The code refers to choice2Property and choice3Property attributes that just do not exist. If you fix the .dist result by replacing them with selected, you get the result you're looking for. The distribution script for this case lacks definitions for some functions that are used to determine the state of choices. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Unfortunately, JavaScript isn't a language that I have yet learned. Looks like I need to buy a good book and learn it. If anyone has a suggestion on a good book that would be relevant to PackageMaker, I'm interested. I asked my wife, who does embedded programming for a living, but her JavaScript experience wasn't recent and it was limited to a web interface on a piece of networking gear. So she wasn't sure either. I tried a couple more things, but I think this is still the same version we were discussing. Before: <?xml version="1.0" encoding="utf-8"?> <installer-script minSpecVersion="1.000000" authoringTool="com.apple.PackageMaker" authoringToolVersion="3.0.3" authoringToolBuild="174"> <title>Bug Demo</title> <options customize="always" allow-external-scripts="no" rootVolumeOnly="false"/> <script> function pm_choice1_selected() { result = true; result = result && (choices.choice2.choice2Property == false); result = result && (choices.choice3.choice3Property == false); return result; }</script> <choices-outline> <line choice="choice1"/> <line choice="choice2"/> <line choice="choice3"/> </choices-outline> <choice id="choice1" title="Choice1" selected="pm_choice1_selected()"> <pkg-ref id="com.pretendco.bugDemo.choice1.pkg"/> </choice> <choice id="choice2" title="Choice2" start_selected="false"> <pkg-ref id="com.pretendco.bugDemo.choice2.pkg"/> </choice> <choice id="choice3" title="Choice3" start_selected="false"> <pkg-ref id="com.pretendco.bugDemo.choice3.pkg"/> </choice> <pkg-ref id="com.pretendco.bugDemo.choice1.pkg" installKBytes="0" version="1" auth="Root">file:./Contents/Packages/choice1.pkg</pkg-ref> <pkg-ref id="com.pretendco.bugDemo.choice2.pkg" installKBytes="0" version="1" auth="Root">file:./Contents/Packages/choice2.pkg</pkg-ref> <pkg-ref id="com.pretendco.bugDemo.choice3.pkg" installKBytes="0" version="1" auth="Root">file:./Contents/Packages/choice3.pkg</pkg-ref> </installer-script> After (Changes in lines 9 & 10 only): <?xml version="1.0" encoding="utf-8"?> <installer-script minSpecVersion="1.000000" authoringTool="com.apple.PackageMaker" authoringToolVersion="3.0.3" authoringToolBuild="174"> <title>Bug Demo</title> <options customize="always" allow-external-scripts="no" rootVolumeOnly="false"/> <script> function pm_choice1_selected() { result = true; result = result && (choices.choice2.choice2Property == selected); result = result && (choices.choice3.choice3Property == selected); return result; }</script> <choices-outline> <line choice="choice1"/> <line choice="choice2"/> <line choice="choice3"/> </choices-outline> <choice id="choice1" title="Choice1" selected="pm_choice1_selected()"> <pkg-ref id="com.pretendco.bugDemo.choice1.pkg"/> </choice> <choice id="choice2" title="Choice2" start_selected="false"> <pkg-ref id="com.pretendco.bugDemo.choice2.pkg"/> </choice> <choice id="choice3" title="Choice3" start_selected="false"> <pkg-ref id="com.pretendco.bugDemo.choice3.pkg"/> </choice> <pkg-ref id="com.pretendco.bugDemo.choice1.pkg" installKBytes="0" version="1" auth="Root">file:./Contents/Packages/choice1.pkg</pkg-ref> <pkg-ref id="com.pretendco.bugDemo.choice2.pkg" installKBytes="0" version="1" auth="Root">file:./Contents/Packages/choice2.pkg</pkg-ref> <pkg-ref id="com.pretendco.bugDemo.choice3.pkg" installKBytes="0" version="1" auth="Root">file:./Contents/Packages/choice3.pkg</pkg-ref> </installer-script> On Mon, Feb 23, 2009 at 5:42 PM, Paul Cook <cook.p.d(a)comcast.net> wrote: I don't intend to reward your help with more work. So feel free to ignore these, unless you want to do otherwise. Also, I only ran the installers far enough to see the effect, not to install anything. Although, except for littering up the root of your partition, I don't expect they would do any harm. Flat Test Case The first, flat, test case has three choices and only choice1 has any requirements. I find the fact that you do things on failure of the test conditions to be a bit confusing. But my goal was to write requirements such that choice1 will become unselected if choice2 or choice3 are selected. Since choice2 and choice3 have no requirements, there is no infinite loop possible. The one big problem with this test case is that I can't seem to get choice1 to be selected as an initial condition. If the requirements are deleted, the Initial State options of the Configuration pane seem to apply. But when I add these requirements, they do not seem to have any effect. Otherwise, this seems to work largely as expected. TEST CASE NESTED This test case has two sets of choices. Choicesa with subchoices choice1 through choice3 and Choicesb with subchoices choice4 through choice6. The choices in choicesa all have requirements that one (or at least I) might expect to implement a radio button behavior. Selecting any one of the three of them causes the other three to become unselected. As above, I can't figure out how to make one of them selected as an initial condition. But even stranger, selecting any of the choices in Choicesb causes all the choices in Choicesa to become unselected. Since there are no requirements referencing choices in Choicesb, it isn't clear why selecting them should should have this effect. This email sent to site_archiver(a)lists.apple.com

1 0

Re: installing daemons on Leopard
by dev.iceberg＠gmail.com 26 Feb '09

26 Feb '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=L2tucZaNxxhteBvF351cck7d29h2cc6TkURTur3s+aI=; b=jh5yRvCyZEi3VWWxbE8bdyqAPNmfEFuGafozjXtyykyfyHx8J6tUfGt/EEzenGS96q qcEzsQq/7rrUZpEUSIse6s8P7qX+8PREFA39nqzaumYvL5AOWJIQcg+CYzIq2uREJWl4 ZF79XJ/0mkOKohqX2R1C8AG9LffDNOWlcUzT4= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=smyS/MptB+F0MBuJnge5PX9ssaZR9o7YMXgv70meBfazVVb4qymC1n3bmM2PyegbVO 57rgDQDogDk7Zg4Spm+NRokGIUHb5I1U3Pon2VliNvQ8pqYyp6I5JQ15PpXERF9v9dQJ 8MdL94Wc5tLCYNzodagfN9KYLwxYpuUuNFFps= On Feb 25, 2009, at 8:55 AM, Greg Neagle wrote: [...] _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… 2) Make sure the archived file has the right owner and permissions when you build the package, and that the bom also lists the correct owner and permissions. Don't let PackageMaker apply its recommended owners and permissions. In addition to that, make sure that the permissions for the daemon executables are root:wheel too. Otherwise, you have a security flaw. This email sent to site_archiver(a)lists.apple.com

1 0

Re: installing daemons on Leopard
by Greg Neagle 25 Feb '09

25 Feb '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com -Greg On Feb 25, 2009, at 7:38 AM, Filippo Ignozza wrote: Ignozza Filippo Digital Video S.p.a. Tel +39 06 43599369 +39 06 4393578 Fax +39 06 43251588 E-mail filippo(a)toonz.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/greg.neagle%40disneyan… _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… 1) Please don't install your daemon in /System/Library/LaunchDaemons; use /Library/LaunchDaemons instead. 2) Make sure the archived file has the right owner and permissions when you build the package, and that the bom also lists the correct owner and permissions. Don't let PackageMaker apply its recommended owners and permissions. Hi, I want to install a daemon on leopard. i am using packagemaker 2.1. After several tests it seems to me that the daemon start if i put a file in /System/Library/LaunchDaemons directory, named myfile.plist. but it seems to me that the system launchs the daemon only if the file myfile.plist has as owner root:wheel.(while everything works fine on Mac osX 10.4 regardless the ownership of the file) Is there a way for me to change with the installer the ownership of the file? Please consider that sometimes i have to install the daemon on machines which do not have root user enabled. any suggestion thanks in advance Filippo This email sent to greg.neagle(a)disneyanimation.com This email sent to site_archiver(a)lists.apple.com

1 0

installing daemons on Leopard
by Filippo Ignozza 25 Feb '09

25 Feb '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Organization: Digital Video S.p.a. Priority: normal Hi, I want to install a daemon on leopard. i am using packagemaker 2.1. After several tests it seems to me that the daemon start if i put a file in /System/Library/LaunchDaemons directory, named myfile.plist. but it seems to me that the system launchs the daemon only if the file myfile.plist has as owner root:wheel.(while everything works fine on Mac osX 10.4 regardless the ownership of the file) Is there a way for me to change with the installer the ownership of the file? Please consider that sometimes i have to install the daemon on machines which do not have root user enabled. any suggestion thanks in advance Filippo Ignozza Filippo Digital Video S.p.a. Tel +39 06 43599369 +39 06 4393578 Fax +39 06 43251588 E-mail filippo(a)toonz.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: What do "Start xyz" options for "On Failure" do?
by Stephane Sudre 25 Feb '09

25 Feb '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UOhQTtuRmAAfGkvWkwhZZbbWkcX+OWmnr5Fxi/vsAzA=; b=qrdmudbhTMlowLt7rQ9uPrUcdHSvyamAxC2h9lWm5tRqoIGs2D1eb/+IiJm7euw2yh RykBJsC8O/LoMmdctE0mTcgi6S1UJkv2fr+EkXwr5dvYE38e2hlg2wPgSg///dUAFgbx FYqYgVKtqOkgtks25JKL9lA1fERtsqWk80IkU= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qag1N/a7CmxBjuq/XdcuAoie3UqHM8aWJHa4q8jIe9f8k7Z3ioxBbKbV+CJa/EJPrM SnyEiGHOpEEKfdqOUIZYV2t7GAJ5gH4vBVRJTM9LzKocABRCsiarET/sD9Z+ZywRYCoW p07Lsl0cS4cQ3BXTf81qr25dIdwnaBc4tB2BY= On Mon, Feb 23, 2009 at 5:42 PM, Paul Cook <cook.p.d(a)comcast.net> wrote: > > I don't intend to reward your help with more work. So feel free to ignore these, unless you want to do otherwise. Also, I only ran the installers far enough to see the effect, not to install anything. Although, except for littering up the root of your partition, I don't expect they would do any harm. > > > > > Flat Test Case > The first, flat, test case has three choices and only choice1 has any requirements. I find the fact that you do things on failure of the test conditions to be a bit confusing. But my goal was to write requirements such that choice1 will become unselected if choice2 or choice3 are selected. Since choice2 and choice3 have no requirements, there is no infinite loop possible. > > The one big problem with this test case is that I can't seem to get choice1 to be selected as an initial condition. If the requirements are deleted, the Initial State options of the Configuration pane seem to apply. But when I add these requirements, they do not seem to have any effect. Otherwise, this seems to work largely as expected. The code generated by PackageMaker is incorrect if the package has not been tampered with after build. The code refers to choice2Property and choice3Property attributes that just do not exist. If you fix the .dist result by replacing them with selected, you get the result you're looking for. > > > > TEST CASE NESTED > This test case has two sets of choices. Choicesa with subchoices choice1 through choice3 and Choicesb with subchoices choice4 through choice6. > > The choices in choicesa all have requirements that one (or at least I) might expect to implement a radio button behavior. Selecting any one of the three of them causes the other three to become unselected. > > As above, I can't figure out how to make one of them selected as an initial condition. But even stranger, selecting any of the choices in Choicesb causes all the choices in Choicesa to become unselected. Since there are no requirements referencing choices in Choicesb, it isn't clear why selecting them should should have this effect. The distribution script for this case lacks definitions for some functions that are used to determine the state of choices. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: What do "Start xyz" options for "On Failure" do?
by Paul Cook 24 Feb '09

24 Feb '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Best Wishes, Paul _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Unless someone has a contrary experience, I don't think that the "Choices" Requirement for a Choice works properly, if at all. If I have choices choice1 through choice6 and I add a requirement to choice1 that choice2 must be false, then resultant package will have the Initial State for choice1 unselected even though the Configuration window may have the Initial State as Selected. When running the resultant installer package, if you manually select choice1, then selecting choice3, choice4, choice5 or choice6 will result in choice1 becoming unselected, even though you provided to requirements that even mention those choices. This email sent to site_archiver(a)lists.apple.com

1 0

Re: What do "Start xyz" options for "On Failure" do?
by Iceberg-Dev 23 Feb '09

23 Feb '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=yP0/1OLyVwjGR1rm2j8jn0CCJx6LIFmVvHUnka3GH3g=; b=NVwToXm12Fnu6del9S7U5qIGlr4UZVnH5Lx/+qbL2iAhpUxS1kRJMWrxuF5wCYhMQS ZtOw0z987VpAye3knlKwUPLDNqfhPLA8k1FZzPV9hVgdXG3AtQ8FRxxR7MbpiHrSjcIk dxN2wvfc0HoCFh/SKPOFb11zjIr4Ib2f15O0o= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=bgEzqX0KxqYRRPu4GmayVvI8Z2DusYlKlHEU1a6x5ahN1SFjYDrHV9rr7qY5T6Vsp9 np7pcS53/lsgdfIn8twtdoBRS6SDxwYW7eY0uge2uXdBk7evFkZ4yENk1i3Xrhr83feM 3tEdMqD6hyPhXG4JmD/EqDIX4fDCcMXdj+jBg= On Feb 23, 2009, at 6:38 PM, Paul Cook wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… I went back and tested some more, and I can't even seem to get the options on the left to work as expected. I'm trying to setup three mutually exclusive choices. Choice1, Choice2, and Choice3. For choice1, I add the requirement that selected is NO, if choice2 is selected. And I also add a requirement that selected is NO, if choice3 is selected. I was expecting to add similar requirements to choice2 and to choice3, but even with just requirements on choice1, the behavior isn't what I expected, or thought I remembered. Is this a bug with 3.0.3. Am I totally confused about what to expect? etc. Thanks in advance for any help. If I understand correctly your needs, you want to have a radio button behavior. I 'm not sure it's possible to do this without introducing an infinite loop. This email sent to site_archiver(a)lists.apple.com

1 0

Re: What do "Start xyz" options for "On Failure" do?
by Paul Cook 23 Feb '09

23 Feb '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thanks in advance for any help. Best Wishes, Paul On Feb 23, 2009, at 10:44 AM, Paul Cook wrote: Again, thanks in advance for any help. Best Wishes, Paul On Feb 23, 2009, at 9:56 AM, Paul Cook wrote: Thanks in advance for any help. Best Wishes, Paul _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/cook.p.d%40comcast.net _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/cook.p.d%40comcast.net _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… I went back and tested some more, and I can't even seem to get the options on the left to work as expected. I'm trying to setup three mutually exclusive choices. Choice1, Choice2, and Choice3. For choice1, I add the requirement that selected is NO, if choice2 is selected. And I also add a requirement that selected is NO, if choice3 is selected. I was expecting to add similar requirements to choice2 and to choice3, but even with just requirements on choice1, the behavior isn't what I expected, or thought I remembered. Is this a bug with 3.0.3. Am I totally confused about what to expect? etc. Oh, and in case it matters, I forgot to say that I'm using Apple's PackageMaker 3.0.3 and my targets are all Leopard. What do "Start xyz" options for "On Failure" of a choice requirement for a Package Install Choice do? If you try to add Requirements to a Package Install Choice, the "On Failure" pane has 3 configurable actions in it on the left side: "Selected", "Enabled", and "Hidden". Each of these has three options: "Unchanged", "Yes" and "No". I think I understand what these do. If the the test fails, these actions change the corresponding "Initial State" selection on the "Configuration" pane for that Package Install Choice. On the right side of the same "On Failure" pane, there are also 3 configurable actions in it on the right side: "Start Selected", "Start Enabled" and "Start Hidden". Each of these also has three options: "Unchanged", "Yes" and "No". I can't seem to figure out exactly what these do. I think part of the problem may be the name. For example, the "Start" in "Start Selected" suggests to me that it has something to do with the initial state of "Selected". But that would seem to be in conflict with the "Initial State" selections that I made back in the "Configuration" pane. Further, they are part of the "On Failure" pane, so that suggests that they are only applied if the test fails. That would seem to make them useless as the actions on the left would immediately over ride them. The January 09 version of the "PackageMaker User Guide" has a brief description of choice requirements on page 23. But it doesn't say what these are about. It refers to the "Software Delivery Guide", but I can't find anything helpful there either. I've tried running a few tests, but haven't seen any results that make sense. Admittedly, part of the problem may be that I may be looking for the wrong thing. This email sent to cook.p.d(a)comcast.net This email sent to cook.p.d(a)comcast.net This email sent to site_archiver(a)lists.apple.com

1 0

Re: What do "Start xyz" options for "On Failure" do?
by Paul Cook 23 Feb '09

23 Feb '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Again, thanks in advance for any help. Best Wishes, Paul On Feb 23, 2009, at 9:56 AM, Paul Cook wrote: Thanks in advance for any help. Best Wishes, Paul _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/cook.p.d%40comcast.net _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Oh, and in case it matters, I forgot to say that I'm using Apple's PackageMaker 3.0.3 and my targets are all Leopard. What do "Start xyz" options for "On Failure" of a choice requirement for a Package Install Choice do? If you try to add Requirements to a Package Install Choice, the "On Failure" pane has 3 configurable actions in it on the left side: "Selected", "Enabled", and "Hidden". Each of these has three options: "Unchanged", "Yes" and "No". I think I understand what these do. If the the test fails, these actions change the corresponding "Initial State" selection on the "Configuration" pane for that Package Install Choice. On the right side of the same "On Failure" pane, there are also 3 configurable actions in it on the right side: "Start Selected", "Start Enabled" and "Start Hidden". Each of these also has three options: "Unchanged", "Yes" and "No". I can't seem to figure out exactly what these do. I think part of the problem may be the name. For example, the "Start" in "Start Selected" suggests to me that it has something to do with the initial state of "Selected". But that would seem to be in conflict with the "Initial State" selections that I made back in the "Configuration" pane. Further, they are part of the "On Failure" pane, so that suggests that they are only applied if the test fails. That would seem to make them useless as the actions on the left would immediately over ride them. The January 09 version of the "PackageMaker User Guide" has a brief description of choice requirements on page 23. But it doesn't say what these are about. It refers to the "Software Delivery Guide", but I can't find anything helpful there either. I've tried running a few tests, but haven't seen any results that make sense. Admittedly, part of the problem may be that I may be looking for the wrong thing. This email sent to cook.p.d(a)comcast.net This email sent to site_archiver(a)lists.apple.com

1 0

What do "Start xyz" options for "On Failure" do?
by Paul Cook 23 Feb '09

23 Feb '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thanks in advance for any help. Best Wishes, Paul _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… What do "Start xyz" options for "On Failure" of a choice requirement for a Package Install Choice do? If you try to add Requirements to a Package Install Choice, the "On Failure" pane has 3 configurable actions in it on the left side: "Selected", "Enabled", and "Hidden". Each of these has three options: "Unchanged", "Yes" and "No". I think I understand what these do. If the the test fails, these actions change the corresponding "Initial State" selection on the "Configuration" pane for that Package Install Choice. On the right side of the same "On Failure" pane, there are also 3 configurable actions in it on the right side: "Start Selected", "Start Enabled" and "Start Hidden". Each of these also has three options: "Unchanged", "Yes" and "No". I can't seem to figure out exactly what these do. I think part of the problem may be the name. For example, the "Start" in "Start Selected" suggests to me that it has something to do with the initial state of "Selected". But that would seem to be in conflict with the "Initial State" selections that I made back in the "Configuration" pane. Further, they are part of the "On Failure" pane, so that suggests that they are only applied if the test fails. That would seem to make them useless as the actions on the left would immediately over ride them. The January 09 version of the "PackageMaker User Guide" has a brief description of choice requirements on page 23. But it doesn't say what these are about. It refers to the "Software Delivery Guide", but I can't find anything helpful there either. I've tried running a few tests, but haven't seen any results that make sense. Admittedly, part of the problem may be that I may be looking for the wrong thing. This email sent to site_archiver(a)lists.apple.com

1 0