Description of problem:
emacs in RHEL 6 requires aspell, however, hunspell is the only supported
spell checker. Oddly, it requires *both* aspell and hunspell.
Version-Release number of selected component (if applicable):
It seems that hunspell is needed for some languages (#443549), and aspell for another ones (#508033).
We should test Emacs with the current (or newer) versions of the dictionaries and try to fix the remaining issues.
After more thinking, my conclusion is that Emacs should require neither aspell, nor hunspell. Emacs' ispell.el is not designed to work out of the box, without configuring it properly. By depending on aspell and hunspell we do not make it easier to configure it.
If both aspell and hunspell are installed and ispell-program-name variable is not set by user, Emacs automatically selects aspell, because it supports it better.
The best way how to setup spell checking in Emacs nowadays is to set ispell-program-name and ispell-dictionary in ~/.emacs, and add installed dictionaries to ispell-dictionary-base-alist (also in ~/.emacs).
The emacs package does not depend on external programs which might be used by various parts of Emacs, such as GDB, pychecker, (La)TeX, and version control systems. Spell checking should not be an exception, especially when it cannot work reliably out of the box.
I have removed both hunspell and aspell dependencies from Emacs in Rawhide, and I think we should do the same for RHEL.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Previously, the emacs packages required the aspell and hunspell spell checkers to be installed. Since the use of a spell checker is completely optional, this update removes aspell and hunspell from the list of dependencies, so that Emacs can now be installed without these packages.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.