If a specified tags file is a symbolic link then the
definition cant' be found if the tag file uses
relative paths for the definition source (that's quite
usual) and the real tag file the symlink points to is
not in the same directory like the symlink.
The patch appended fixes this by simply resolving
the tags files path just before loading it. For the
user nothing (exept more tags will be found ;-) nothing
changes - especially the original logical tags file
path (i.e. the symlink) remains visible in the menus.
I don't know if resolvepath() is defined on all
systems we use.