xemacs and ctags conflict

[ilevy@…]

Hi all,

newbie to macports / mac. I'm trying to install xemacs and macvim (overkill, I know, since I should just choose one). Anyway, if I have one activated and try to install/activate the other, I get:

--->  Activating xemacs @21.4.22_2
Error: Target org.macports.activate returned: Image error: /opt/local/bin/ctags is being used by the active ctags port.  Please deactivate this port first, or use 'port -f activate xemacs' to force the activation.
Log for xemacs is at: /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_xemacs_21.4.22_2/main.log
Warning: Failed to execute portfile from registry for xemacs @21.4.22_2
--->  Activating xemacs
Error: port activate failed: Image error: /opt/local/bin/ctags is being used by the active ctags port.  Please deactivate this port first, or use 'port -f activate xemacs' to force the activation.

The log file doesn't have any more information. I did have a weird python install, if that makes a difference. I installed python2.7 from their website as a normal installer, and it put it's own path in my .profile. So python actually linked to 2.7 instead of what macports thought.

But besides that everything is fairly standard.

[ilevy@…]

all three files the same, accidental duplicates..

[ilevy@…]

sorry for omitting: Hardware is MacBook 4.1 (intel core 2 duo) / snow leopard

[jmroot (Joshua Root)]

Please remember to preview and use WikiFormatting, and to cc the maintainer.

[deric@…]

FreeBSD and others I know solves this by installing Exuberant Ctags as exctags

[petrrr]

Hi, any chance that this ticket gets addressed? The conflict is still present.

[petrrr]

Cc Me!

[vallon (Justin)]

Patch to not install ctags & man1/ctags.1

[vallon (Justin)]

Port:emacs does not install ctags. Attached a patch for xemacs/Portfile that will remove ctags and man1/ctags.1 from destroot.

Alternative approaches: add a no_ctags variant; or, rename it to ctags.${tag} (ctags.xemacs)

[vallon (Justin)]

Cc Me!

[dstrubbe (David Strubbe)]

As far as I know, this problem was fixed years ago. I was not aware of the existence of this ticket. If anyone thinks it is a problem, please provide updated evidence that something is going wrong.