The easies way to simulate symbolic links would be to have your build
system create copies of the appropriate file trees as an initial build step.

Note that the enhancement request for symbolic link support (40443)
recently was targeted for the 2.0.0.2 release, so it currently is in-plan.

But note that this would provide version control of symbolic links on a
platform (i.e. Unix) that supports symbolic links. It wouldn't try to
simulate symbolic links on file systems that don't support them (e.g. as
ClearCase does by making copies, or in the case of CC dynamic views,
actually implement them). So when you are asking for symbolic link
support, do you just want them to be able to be captured as a version,
and then restorable only on file systems that support symbolic links, or
were you asking for the ClearCase-style simulation of symbolic links via
copies? For the latter approach (simulation by copies), there I'd
suggest you just use the build approach, suggested earlier, rather than
trying to get the versioning system to do them.

Cheers,
Geoff



hajo62 wrote:

Lets think about two components.
Is there a way to have the component 2 linked into the directory
structur of component 1 like I can do this in ClearCase?

I learned, that RTC does not support symbolic or hard links.
Is there a best practice how to handle this use case?
Are there plans to have a links feature in the (near) future?

Regards
Hajo