site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com In message <AD1592D8-73F7-4A38-B9B3-A2CD67857D9B@apple.com>, Dave Zarzycki writ es:

I don't believe any of us ever said that they were unimportant. Broken, yes, unimportant no. If anybody suggested the latter, I'm sorry.

Well, if the answer to "how do I run my existing program which I don't own or control the source to, which runs on all my other systems fine" is "start maintaining local patches yourself or coerce the developer to introduce Mac-only support code", that sort of feels like "unimportant".

On the matter of dependencies and ordering, let's be fair here. launchd DOES provide a mechanism for such scenarios. Yes, it is different than the old-school Unix rc.d/StartupItem view of the universe, and yes, one can't just switch to launchd from the old way without some small amount of code changes, but it does support dependancies and ordering.

I'm really confused. Half the time, I'm told launchd supports these things, but requires code changes, half the time, I'm told it doesn't. It sounds very much like the "support" launchd provides for dependencies is "if you want to do the ordering yourself, we won't stop you". Is this something one could do with trivial wrappers, at least? An ordering wrapper that allowed an admin to avoid touching a third-party program would be awfully cool. -s _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com