Hello,
I recently received a feature request to add "+emacs_app" option to
gnuplot in addition to "+emacs":
http://trac.macports.org/ticket/36135
Everything that either option does is installing the following files:
/opt/local/share/emacs/site-lisp/gnuplot-gui.el
/opt/local/share/emacs/site-lisp/gnuplot-gui.elc
/opt/local/share/emacs/site-lisp/gnuplot.el
/opt/local/share/emacs/site-lisp/gnuplot.elc
/opt/local/share/emacs/site-lisp/info-look.20.2.el
/opt/local/share/emacs/site-lisp/info-look.20.3.el
The only difference between "emacs" and "emacs_app" is that in case of
"emacs_app" one has to set
configure.env-append
EMACS=${applications_dir}/Emacs.app/Contents/MacOS/Emacs
since the user doesn't have "emacs" in PATH, but that variable/binary
is only needed to perform some trivial tasks during
configuration/installation. Once the installation is finished there is
no difference in what the original selection was (/opt/local/bin/emacs
or /Applications/MacPorts/Emacs.app/Contents/MacOS/Emacs). There is
just a bunch of text files installed into
/opt/local/share/emacs/site-lisp.
>From that point of view it seems a bit of an overkill to me to provide
two options (result doesn't depends on which one was selected), it is
only important that at least one emacs binary is present on the system
and its full path is exposed to gnuplot.
Does this call for an Emacs PortGroup with ${emacs_binary} variable?
Any other suggestion? (One solution would definitely be to fix gnuplot
in such a way that it wouldn't even have to call emacs, it would just
copy the files, but that's an even bigger overkill.)
Thank you,
Mojca
Disclaimer: I'm not an emacs user and don't know anything about
emacs-related ports. I'm just relying on feedback that Jaminos
provided in:
"Well, the way I wrote the emacs_app variant, the files end up in
${prefix}/share/emacs/site-lisp, not inside Emacs.app. IIRC that used
to be required, but at some point the emacs-app maintainers fixed its
load-path to include both Emacs.app/Contents/Resources and
${prefix}/share/emacs. I think the theory was that eventually we
wouldn't need separate "emacs" and "emacs_app" variants for other
packages, but clearly there are still some issues when we need the
executable itself and not just the location of the site-lisp
directory."
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
