From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
Description of problem:
Emacs uses its own "Emacs TAGS" tags format (as opposed to "VI tags")
These TAGS files are generated by "etags" program which comes with Emacs.
This program is incorrectly installed as "/usr/bin/etags.emacs"
instead or "/usr/bin/etags".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: no such program
Expected Results: Emacs TAGS file is generated
Apparently you are confused by the fact that Emacs also offers an
implementation of the standard "VI tags" in file ctags (which you
install as "/usr/bin/ctags.emacs" because anther package already
provides a ctags executable.
You have to install "etags" as "/usr/bin/etags".
No, the problem is that both Emacs and XEmacs provide etags.
Currently the emacs-common %post script is supposed to create
a symlink etags -> etags.emacs if etags doesn't exist.
This works with emacs-common is installed at least - not sure
how well it works with upgrading the first time because rpm
removes the old files *after* the new package is installed
which I believe is after %post is run. So the first time
emacs-common gets upgraded the symlink will probably not be created
unfortunately. It should happen the next time emacs-common
is upgraded or of course you can create it yourself.
The right way to do this is to use alternatives, hopefully
that will happen for FC3.
*** This bug has been marked as a duplicate of 92256 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.