From IRC conversation: [Sat Oct 5 2019] <@graaff> ulm: you may be interested in emacs-libvterm in my graaff overlay <@graaff> it uses a module but I don't think the elisp eclasses have support for that yet? <@ulm> graaff: I'm going to look into it <@graaff> Proper terminal emulation rather than what M-x shell does [Fri Oct 18 2019] <@ulm> graaff: sorry for the delay, I just found time to look at emacs-libvterm <@ulm> installing the module under ${SITELISP} doesn't look right to me <@ulm> it should be in /usr/lib* <@ulm> emacs uses dlopen, I suppose? so should use normal library path? <@ulm> hm, it doesn't but seems to use load-path <@ulm> graaff: so, here's a plan :) <@ulm> I'd suggest to install any modules in /usr/$(get_libdir)/emacs/site-modules/${PN} <@ulm> elisp-common.eclass would have support for the correct exeinto and doexe calls, and for adding the dir to load-path <@ulm> or should we omit the site-modules level, i.e. install to /usr/$(get_libdir)/emacs/${PN}? <@ulm> that won't correspond to the hierarchy in site-lisp though
Upstream discussion: https://lists.gnu.org/archive/html/emacs-devel/2019-10/msg00871.html
This has been fixed some time ago: commit 52fcc6b583bd158b7ff83789a5e9dbd24c0f2599 Author: Ulrich Müller <ulm@gentoo.org> Date: Sat Jul 25 21:08:45 2020 +0200 elisp-common.eclass: Support installation of dynamic modules. Signed-off-by: Ulrich Müller <ulm@gentoo.org>
