We want to intentionally use the absolute->relative symlink fixups, because builds with modified (say) '%(bindir)s' macros might cause the number of leading '../' path segments to be wrong.  By allowing these absolute symlinks in recipes and then fixing them up after the fact, recipe writers do not have to write code to count the path segments to make recipes work even with redefined path elements.
We want to intentionally use the absolute->relative symlink fixups,
because builds with modified (say) '%(bindir)s' macros might cause
the number of leading '../' path segments to be wrong.  By allowing
these absolute symlinks in recipes and then fixing them up after
the fact, recipe writers do not have to write code to count the path
segments to make recipes work even with redefined path elements.

With this change, it becomes RECOMMENDED that symlinks involving
path macros be made as ABSOLUTE symlinks unless there is some
specific reason why not.

sassoftware/conary,sassoftware/conary,sassoftware/conary,sassoftware/conary,sassoftware/conary