Description of problem: XEmacs packages xemacs and xemacs-nox both have a Provides: xemacs(bin) so that when packaging an add-on package which does not care about Xorg support you can simply have a Requires: xemacs(bin). No such facility currently exists for emacs and emacs-nox. An approximation to this is to have Requires: emacs-common in add-on packages, since emacs and emacs-nox both Require:emacs-common. But, then you could install your add-on package, have it pull in emacs-common, but that wouldn't pull in emacs or emacs-nox. User scratches head.
RFE seconded. But I should also mention that I'm not particularly proud of xemacs(bin) as the name for the Provides, the "bin" isn't really very descriptive. If someone can come up with something significantly better, I'm open to changing that in the XEmacs packages too. Perhaps emacs(ui), emacs(main), or emacs(impl), or emacs(your_suggestion_here)? I can live with "bin" though. Also, if the Provides are added to the main emacs and emacs-nox packages, a dependency on it can be added to emacs-common like "Requires: emacs(bin) = %{version}-%{release}" which makes sure emacs-common won't be installed without an actual Emacs editor. I haven't done that in the xemacs-common package; not sure why - I'll look into it.
Possible virtual provides names I can think of (none of which I feel any more passionate about really): emacs(editor) emacs(frontend) emacs(program) or if we don't need ()s' emacs-editor emacs-frontend emacs-program
Hi Chip, Ville - it would be nice if we could resolve this one so that we can finalize the packaging guidelines for emacsen add on packages.
Added in 22.1-2.
This is resolved, closing bug.