site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Jun 2, 2006, at 10:16 AM, Peter Seebach wrote: Dave - has nothing new to add to this conversation - Zarzycki _______________________________________________ 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... 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". Sigh... This has been discussed ad nauseam and our story hasn't changed. If one wishes to run legacy programs unmodified, then one should use StartupItems. 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? If you don't care about robustness, sure. But like I said earlier, we're going round and round in circles. Yes, Apple understands that the switch to launchd has caused a few IT professions grief as they find themselves caught in the middle of the legacy software clashing with modern OS design, but we hope that pain will be temporary. This email sent to site_archiver@lists.apple.com