putting virtual/emacs in /etc/portage/package.provided does not work. Perhaps eselect should do the proper thing to show the virtual/emacs is installed if one eselects xemacs rather than emacs. Reproducible: Always Steps to Reproduce: 1.emerge xemacs 2.spanker etc # eselect emacs set xemacs 3.emerge slime Actual Results: installs app-editors/emacs Expected Results: only installs slime
"SLIME works with GNU Emacs versions 21 and 22 and with XEmacs version 21 on Unix, OSX, and Win32." The short answer is that emacs isn't xemacs, but you're right if you put it that according to the [URL], slime could depend on xemacs instead of emacs... elisp.eclass would need to change, though.
All those dual-use utilities ([x]emacs modes) should depend on some common virtual. I would propose that: 1. app-editors/emacs be renamed app-editors/gnu-emacs 2. virtual/xemacs be eliminated 3. whichever version of emacs (including sxemancs, for instance) install virtual/emacs 4. all emacs modes/utilities depend on virtual/emacs. What do you think? -Kevin
This cannot be done in the suggested way for several reasons. XEmacs and Emacs are expecting packages in different directories (/usr/share/emacs vs /usr/lib/xemacs) and their byte-compilers have subtle differences, so that the .elc files are not interchangeable. (In reply to comment #2) > All those dual-use utilities ([x]emacs modes) should depend on some common > virtual. No, see above. > I would propose that: > > 1. app-editors/emacs be renamed app-editors/gnu-emacs Why? Upstream calls the package "Emacs" and we have no reason to use a different name. Also, no other major distro calls the package "gnu-emacs". > 2. virtual/xemacs be eliminated > 3. whichever version of emacs (including sxemancs, for instance) install > virtual/emacs > 4. all emacs modes/utilities depend on virtual/emacs. This won't work, see above. For SLIME support in XEmacs, you would want a separate package app-xemacs/slime. Reassigning to the XEmacs team.
(In reply to comment #3) > For SLIME support in XEmacs, you would want a separate package > app-xemacs/slime. It's more complicated since the Emacs and the XEmacs package would collide, so one would have to split off dev-lisp/swank: <ulm> fe[nl]ix: bug 240327 <Willikins> ulm: https://bugs.gentoo.org/240327 "app-xemacs/slime ebuild request"; Gentoo Linux, Ebuilds; NEW; seabrightskiff@gmail.com:xemacs@g.o <fe[nl]ix> ulm: I've seen it :D <fe[nl]ix> wacky <ulm> fe[nl]ix: I wonder how to do that if we really would want such a thing <ulm> since app-emacs/slime and app-xemacs/slime would both install colliding files in some cl directories <fe[nl]ix> splitting dev-lisp/swank from app-emacs/slime is doable <fe[nl]ix> for instance, it's what debian does <fe[nl]ix> but the fact is that slime devs use gnu emacs <ulm> yeah, that's what I thought <fe[nl]ix> and don't bother about testing on xemacs <ulm> graaff: any objections if I assign that bug to m-w? <fe[nl]ix> I think there's one dev who uses xemacs but I'm not sure <graaff> ulm: not at all
It seems like this can be closed as OBSOLETE or WONTFIX for two reasons: 1) it has been almost a decade 2) slime no longer supports xemacs at all. Reference: https://common-lisp.net/project/slime/doc/html/Platforms.html#Platforms
Closing due to the reasons pointed out. Thanks for the analysis.
