FS#2144 - ctags PKGBUILD sets a conflict with emacs
Attached to Project:
Arch Linux
Opened by Ferenc Deak (feco) - Sunday, 06 February 2005, 12:27 GMT
Last edited by Dale Blount (dale) - Sunday, 06 February 2005, 17:26 GMT
Opened by Ferenc Deak (feco) - Sunday, 06 February 2005, 12:27 GMT
Last edited by Dale Blount (dale) - Sunday, 06 February 2005, 17:26 GMT
|
Details
Problem:
The PKGBUILD of the Ctags package sets a conflict with the emacs package, which means that if you install emacs, you can't use any other editor's ctags feature because almost all of the editors other than emacs use the ctags file with the "classic" format created by exuberant ctags. It means that virtually every editor using ctags conflicts with emacs, if you would like to use it for serious development. Possible solutions: Install the exuberant ctags executable and manual file under the name ctags-exuberant (also) or Force ctags to only install 'ctags' and force emacs to only install 'etags', and not install/destroy its counterparts. But I don't know whether emacs uses the executable named 'ctags' or it is using 'etags' only. It needs an emacs expert to decide... or Simply use exuberant ctags as 'etags' for emacs also (because it can generate etags-style tags file). Ctags installs itself as etags by default too. And before the install we simply ask a question, like this "With installing ctags you are about to overwriting the emacs's etags, which is normaly doesn't hurt, but..." It also needs an emacs expert to decide. or ... All in all I think we have to allow to exist ctags AND emacs paralel without a conflict somehow... |
This task depends upon
Closed by Simo Leone (neotuli)
Sunday, 15 October 2006, 18:00 GMT
Reason for closing: Fixed
Additional comments about closing: updated ctags
Sunday, 15 October 2006, 18:00 GMT
Reason for closing: Fixed
Additional comments about closing: updated ctags
emacs /usr/bin/ctags.emacs
emacs /usr/bin/etags.emacs
So you can remove the conflicts array in the next ctags release.
Jürgen