<snip>
I'm not quite sure what you're saying, but if miniAudicle installs a
ChucK in /usr/local/bin, then I don't see a reason to have a separate
package just for command-line ChucK.
The command-line version of Chuck iterates a while before the one in miniAudicle catches up. Sometimes a while goes by and you're using the latest chuck on the command-line and the previous one in miniAudicle. That's one reason.
But I don't think that miniAudicle puts a binary of chuck in /usr/local/bin, I think it keeps it's own binary as part of the .app file package, which is where that binary belongs. I'm not sure what the story is with how miniAudicle gui communicates with the chuck process, but it's possible that it's version of chuck is modified to accomodate that. Spencer?
-Mike