Opened 12 years ago

Closed 12 years ago

Last modified 3 years ago

#38044 closed defect (fixed)

ctags and developer_cmds should be marked as conflicting (and vim should be able to depend on either)

Reported by: cooljeanius (Eric Gallager) Owned by: larryv (Lawrence Velázquez)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: mww@…, mfeiri, raimue (Rainer Müller)
Port: ctags developer_cmds vim vim-app MacVim

Description

They both try to install an executable named ctags into ${prefix}/bin. Either they should both be marked as conflicting with one another, or since the ctags port is Exuberant Ctags specifically, it could have the name of its executable renamed accordingly. If they get marked as conflicting, all ports that depend on ctags should be updated so either ctags or developer_cmds could fulfill that dependency. For example, the vim port currently has port:ctags as a dependency in its portfile, while it should probably have path:bin/ctags:ctags listed instead.

Change History (7)

comment:1 in reply to:  description Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to egall@…:

If they get marked as conflicting, all ports that depend on ctags should be updated so either ctags or developer_cmds could fulfill that dependency.

Are they the same program, or two unrelated programs that happen to have the same name?

comment:2 Changed 12 years ago by larryv (Lawrence Velázquez)

Replying to ryandesign@…:

Are they the same program, or two unrelated programs that happen to have the same name?

They’re different. I assume developer_cmds provides standard Apple utilities, which means it provides BSD ctags; ctags installs Exuberant Ctags.

Why does vim depend on ctags anyway?

comment:3 in reply to:  2 ; Changed 12 years ago by cooljeanius (Eric Gallager)

Replying to larryv@…:

ctags installs Exuberant Ctags.

Why does vim depend on ctags anyway?

If you follow the link you linked to, there should be a link on it to the following page that explains how vi and its clones use ctags: http://oreilly.com/catalog/vi6/chapter/ch08.html#ch08_05.htm

comment:4 Changed 12 years ago by raimue (Rainer Müller)

Port: vim-app MacVim added

According to r35945, I added the dependency based on results from trace mode. Taking a closer look now, this seem bogus as the configure script only checks for the variant of ctags in order to generate tags for the source itself.

Dependency removed from vim, vim-app and MacVim in r103106.

The conflict between ctags and developer_cmds remains.

comment:5 in reply to:  3 Changed 12 years ago by larryv (Lawrence Velázquez)

Owner: changed from macports-tickets@… to larryv@…
Status: newassigned
Version: 2.1.3

Replying to egall@…:

If you follow the link you linked to, there should be a link on it to the following page that explains how vi and its clones use ctags:

I’m aware of how to use ctags with vi; I just (correctly) doubted the need for vim to have a library dependency on it.

comment:6 Changed 12 years ago by larryv (Lawrence Velázquez)

Resolution: fixed
Status: assignedclosed

Marked as conflicting in r103109.

comment:7 Changed 3 years ago by cooljeanius (Eric Gallager)

Note that the part about vim's dependency on ctags also applies to source-highlight @3.1.9_1 and global @6.6.6

Note: See TracTickets for help on using tickets.