[Bug 290546] [NEW PORT] comms/emacs-eat: Emulate A Terminal

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290546

Joseph Mingrone <jrm@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jrm@freebsd.org

--- Comment #2 from Joseph Mingrone <jrm@freebsd.org> ---
This looks like a pretty cool project.  Thanks for porting it.

I have one concern.  With USES=emacs:build, the byte-compiled elisp (.elc) will
always be generated with editors/emacs, but there will be no run-time
dependencies.  This means a user is free to install emacs-eat and run it under
editors/emacs-devel.  However, byte-compiled elisp is not stable across Emacs
versions, so compiling with one Emacs and loading with another can lead to
subtle breakage.  The workaround is to change USES=emacs:build to USES=emacs,
which I can do on commit.

## An aside about our elisp ports/packages

I appreciate the motivation to simplify things.  It would be nice to have
simple elisp ports like this without a package for each flavor of editors/emacs
and each flavor of editors/emacs-devel.  However, if we want users to be able
to `pkg install <elisp-package>` and include byte-compiled code, I think this
is the only way to go until our package system supports something like
provide/requires.  Once that happens, we will only need two packages for each
elisp port, one for editors/emacs and one for editors/emacs-devel.

Given native-compiled elisp is becoming more popular, and the .eln cache is
usually stored under the user's home directory, we could consider not
installing the byte-compiled .elc files, as, for example, you do in
devel/rust-mode.  Another possibility, floated by ashish@, is to investigate
generating the byte-compiled files on the target host during installation of
elisp packages and Emacs itself.

-- 
You are receiving this mail because:
You are the assignee for the bug.