site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Jun 16, 2006, at 11:49 AM, Finlay Dobbie wrote: I think Dave meant that you should use an alternative to LaunchAgents, such as programmatically modifying the login items, which is supported and should work in future releases of the operating system, current versions of the operating system and previous versions of the operating system. Going forwards, once LaunchAgents work properly (in Leopard), you should think about transitioning to them. At this point in time, it's probably best not to try and implement a LaunchAgent. Let's imagine this technology works fine on Leopard. Let's imagine some software need to be both 10.4 and Leopard compatible. I know backward compatibility is so yesterday these days but... _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... On 16/06/06, Stephane Sudre <ssudre@intego.com> wrote:
I'm terribly sorry to report that LaunchAgents are for all practical
purposes, busted in Tiger. I'd advise against using them until
Leopard. Sorry. Stupid question, how could one do that? Since it's a .plist and I don't
remember seeing a minimum OS version key, what would be the solution to prevent it from running on 10.4? This is how I read it in the first place. The question was more about backward compatibility: How can you prevent your Launch Agent from being "launched" on 10.4 because of possible bugs? Since it looks like the purpose of launch agent is to just automatically run a task, does that mean that you need to manually run the task at least once to see if you can run it automatically later. This seems to defeat the automatic goal. This email sent to site_archiver@lists.apple.com