[MacPorts] #36135: gnuplot enhancement to support emacs-app

[MacPorts]

#36135: gnuplot enhancement to support emacs-app
--------------------------+------------------------------------
  Reporter:  jrh@…        |      Owner:  mojca.miklavec.lists@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.1.2
Resolution:               |   Keywords:  haspatch
      Port:  gnuplot      |
--------------------------+------------------------------------

Comment (by jrh@…):

 Replying to [comment:10 mojca.miklavec.lists@…]:
 > My main remaining question (apart from PortGroups etc) is: do emacs
 users really care that much if they have to install {{{emacs}}} in
 addition to {{{emacs-app}}} to get the gnuplot mode for emacs working in
 Emacs.app, so that it would justify an extra option (additional
 complexity) for the port?

 Well, it does strike me as a bit annoying to have to build/install emacs
 twice (and then keep updating both). But I understand your perspective,
 too. It seems like if there's any complexity to be had, it should be
 handled by the emacs packages and not ones merely with emacs dependencies
 (gnuplot, php-mode.el, etc).

 Does your 4.6.1 Portfile specify {{{path:share/emacs/site-lisp:emacs}}}
 instead of {{{path:bin/emacs:emacs}}}? With that in place, perhaps it
 would be enough if I set EMACS in my environment before calling {{{port
 install gnuplot +emacs}}}. (Does the build inherit the caller's
 environment?)

 It seems like all this could go away if:
 1. The emacs-app port were listed as a conflict with the emacs port (the
 way xemacs is).
 2. It installed something like this script into {{{${prefix}/bin/emacs}}}:
 {{{
 #!/bin/sh
 exec /Applications/MacPorts/Emacs.app/Contents/MacOS/Emacs -nw "$@"
 }}}

 But maybe I'm missing something that's really obvious to the true Emacs
 weenies.

-- 
Ticket URL: <https://trac.macports.org/ticket/36135#comment:11>
MacPorts <http://www.macports.org/>
Ports system for Mac OS