<div dir="ltr">Hey Joshua,<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:12.8000001907349px">1. is really the only reasonable option. Whether you do it now or</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">someone else does it later, it's what we want to have in an app whose</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">target audience includes users who don't want to use the terminal.</span></blockquote><div><br></div><div>I tried to keep the discussion more towards the implementation of it, as I could potentially create a launcher, or go through other ways to make it so you don't have to use the terminal to launch the GUI application (or visa versa). </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:12.8000001907349px">MacPorts.framework still uses a privileged helper tool to do the things</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">that require root, right? Why couldn't it be run in this way?</span></blockquote><div><br></div><div>Uhhh, no, not as far as I know. The privileged helper is needs to be communicated with through the IPC library, which wouldn't be possible if it was launched through a shell. </div><div><br></div><div>-Kyle</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 7, 2015 at 1:48 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 05:23 , Kyle Sammons wrote:<br>
> Hey Ian,<br>
><br>
> Thanks for the offer, unfortunately, however, Pallet doesn't run any<br>
> shell commands (everything is passed done through spinning up a Tcl<br>
> shell and passing input/output through IPC), so I'm afraid your example<br>
> wouldn't work.<br>
<br>
</span>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>
- Josh<br>
</blockquote></div><br></div>