<div dir="ltr">Hey Joshua,<div><br></div><div>Sorry to get back to you late, I was with family this weekend. </div><div><br></div><div>Anyhow, from how I understand it, the application must be started internally in-order to get the IPC setup correctly. However, I'm not terribly well versed in the internals of the IPC framework, so I can't be 100% sure about that.</div><div><br></div><div>-Kyle</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 7, 2015 at 3:23 PM, Joshua Root <span dir="ltr"><<a href="mailto:jmr@macports.org" target="_blank">jmr@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2015-8-8 07:35 , Kyle Sammons wrote:<br>
> MacPorts.framework still uses a privileged helper tool to do the things<br>
> that require root, right? Why couldn't it be run in this way?<br>
><br>
><br>
> Uhhh, no, not as far as I know. The privileged helper is needs to be<br>
> communicated with through the IPC library, which wouldn't be possible if<br>
> it was launched through a shell.<br>
<br>
</span>Why not? Doesn't it just use a unix socket?<br>
<br>
- Josh<br>
</blockquote></div><br></div>