On Sep 13, 2009, at 15:02, Jeremy Lavergne wrote:
I propose that we avoid using daemondo only if the portfile
explicitly uses launchd, maintaining backwards compatibility. Any
thoughts on this?
You mean flag in the Portfile to indicate if daemondo should be
used or not?
Indirectly: I mean to use the existing startupitem.type (launchd,
startupitem, etc). If it's type launchd then we already expect
launchd's behavior and the added wrapping is wasteful. For this
instance (or any others we deem "safe" to change) we should just
create launchd scripts without daemondo being involved.
There are only three ports that use "startupitem.type" (murmur and
denyhosts) and they both set it to the default "launchd".
Based on what Joshua said:
On Sep 12, 2009, at 10:06, Joshua Root wrote:
It is impedance matching for daemons that aren't happy being managed
by
launchd directly. That's all.
I assume this means there are ports that would not work right when
managed directly by launchd. Can anybody think of any examples of this?
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
