Not really MacPorts problem, I don't think.

[William H. Magill]

> On Jan 23, 2015, at 2:36 AM, Joshua Root <jmr at macports.org> wrote:
> 
>> At 8:42 PM -0600 1/22/15, Ryan Schmidt wrote:
>>> So launchd is launching apache too early. I believe there are some 
>>> keys one can use in a launchd plist that would affect when launchd 
>>> tries to launch a service. If you can find a launchd plist key/value 
>>> that fixes this issue, MacPorts could be enhanced to offer portfile 
>>> authors a way to use that key, or to use that key/value by default 
>>> even.
>> 
>> I'm not expert, but would the NetworkState key help?  See:
>> 
>> http://launchd.info/
>> 
>> Goto "Configuration", scroll down to "...Depending on Network Availability:"
> 
> We do have startupitem.netchange.

I'm confused.

The implication of "startupitem.netchange" :
"Cause the daemon to be restarted when a change in network state is detected."
                   https://guide.macports.org/chunked/reference.startupitems.html

is different from "NetworkState"
"Setting this subkey to true will start the job when/while any network is/becomes available. Setting this subkey to false will start the job when/while all network connections are down."
                   http://launchd.info

And there is no indication on the guide.macports.org page as to what the output of "startupitem.netchange" might generate.

i.e. no translation between the syntax of launchd and startupitems.

T.T.F.N.
William H. Magill
# iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.10.1
# Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.10.1 OSX Server (now dead)

magill at icloud.com
magill at mac.com
whmagill at gmail.com