<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 01/11/2014 16:35, Dave Horsfall
wrote:<br>
</div>
<blockquote
cite="mid:alpine.BSF.2.00.1411020327040.84102@aneurin.horsfall.org"
type="cite">. . . . </blockquote>
<blockquote>Don't you get start-up messages like this?
<br>
<br>
| DaveHorsMacBook% gimp
<br>
| Error spawning command line `launchctl getenv
DBUS_LAUNCHD_SESSION_BUS_SOCKET': Child process killed by signal
11
<br>
| Dynamic session lookup supported but failed: launchctl
terminated abnormally without any error message
<br>
| Not enough memory
<br>
| <br>
| (gimp:2988): LibGimpBase-WARNING **: gimp: gimp_wire_read():
error
<br>
| <br>
| (gimp:2988): LibGimpBase-WARNING **: gimp: gimp_wire_read():
error
(Zillions of them, as Gimp checks plug-in after plug-in, whilst
appearing to access the Net.)
<br>
</blockquote>
. . . . <br>
<br>
If I go to the the command line and type gimp, then yes I get
exactly these messages too. Without a lot of research, I couldn't
tell you what they mean - but when gimp is eventually running it
seems to work OK.<br>
<br>
However I never noticed these messages with gimp before because I
always used the launcher GIMP.app in /Applications/MacPorts and it
presumably discards non-fatal error messages. In my experience of
MacPorts, many applications spew out non-fatal error messages during
launch - but if they ever get to open the main window, they are
usually OK to use.<br>
<br>
By the way, did you look in /Applications/MacPorts to see if you
have the GIMP.app launcher there?<br>
<br>
You also asked:<br>
<blockquote>. . . . . <br>
</blockquote>
<blockquote>
<pre wrap="">
Speaking of launchers, is there an Idiot's Guide to it anywhere? Apple
appear to have gone out of their way to abolish such fine old institutions
like /etc/inetd.conf, /etc/crontab, /etc/fstab etc...
.........
</pre>
</blockquote>
<blockquote
cite="mid:alpine.BSF.2.00.1411020327040.84102@aneurin.horsfall.org"
type="cite">
</blockquote>
You ask if there is "an Idiot's Guide to it" - but I am not sure
what you are referring to by "it". Are you asking about Apple MacOSX
or MacPorts. MacPorts goes out of its way to put its stuff in
different places to MacOSX so that neither will mess up the other's
files during updates. MacPorts also steers clear of places where
other Open Sources software might install - e.g. the MySQL you get
direct from <a class="moz-txt-link-abbreviated" href="http://www.mysql.com">www.mysql.com</a> installs into /usr/local so it doesn't
conflict with MySQL installed through MacPorts<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<br>
If you want to understand where MacPorts puts its stuff then it is
implied in Section 2.4 of the MacPorts manual which gives the
command for completely ripping a MacPorts installation from your
system:<code class="prompt"><br>
</code>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<pre class="programlisting"><code class="prompt">$</code> <strong class="userinput"><code>sudo rm -rf \
/opt/local \
/Applications/DarwinPorts \
/Applications/MacPorts \
/Library/LaunchDaemons/org.macports.* \
/Library/Receipts/DarwinPorts*.pkg \
/Library/Receipts/MacPorts*.pkg \
/Library/StartupItems/DarwinPortsStartup \
/Library/Tcl/darwinports1.0 \
/Library/Tcl/macports1.0 \
~/.macports</code></strong></pre>
which is why the launchers for MacPorts apps go into
/Applications/MacPorts, rather than being sprinked all over
/Applications itself.<br>
<br>
I hope this helps<br>
<br>
David Rowe<br>
</body>
</html>