Re: StartupItems
Re: StartupItems
- Subject: Re: StartupItems
- From: email@hidden (Peter Seebach)
- Date: Sat, 03 Jun 2006 15:22:43 -0500
In message <email@hidden>, "Benj
amin Reed" writes:
>I think the fundamental thing that's confusing about your argument is
>that your software already has to *know* how to *use* these resources,
>so why does it seem strange to you to also ask for them at runtime?
For a lot of them, the way to ask for them is Mac-only.
>It's not like you expect to be able to write a bittorrent client by
>making a configuration file that says "this is a bittorrent client"
>and it magically does everything for you. There's some point at which
>your software's logic determines the resources needed, and you have to
>ask for them. Just because some of them were previously assumed
>doesn't mean it was correct to do so.
Yeah, but it was CONVENIENT.
>Now, if you were saying "why isn't there an API where in a one-liner I
>can ask for the startup volume to be available?" that would be a good
>question. But saying "why can't I just pretend the resources are
>there because I used to be able to" is counterproductive, even if it's
>been traditionally true on other *NIXen.
It may be... But not allowing jobs to wait on dependencies, when we KNOW that
many jobs want to be run that way, is also counterproductive. Offering a
choice would be good.
>If launchd could magically know how the system can support your
>software you'd be out of a job, it would be an AI that wrote your
>software for you. :)
I'm okay with a configuration file. I just want to be able to have launchd
do the code for the common cases.
-s
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden