symlink with RTC

You cannot currently create symlinks from the RTC scm command line tool.
You would just create symlinks in your RTC sandbox, and then check in
that symlink to put it under version control.

Note that in 3.0.1, you can only put symlinks in a Unix sandbox under
version control. In 4.0, you will be able to symlinks in a Windows
sandbox under version control.

Cheers,
Geoff

On 11/20/2011 11:38 AM, gsokhi wrote:

Does RTC has symlink capability like cleacase ie cleartool ln

Bit confused.
Are you saying with 3.0.1 symlink are only supported in UNIX via RTC GUI and not RTC SCM CMD command line?

You cannot currently create symlinks from the RTC scm command line tool.
You would just create symlinks in your RTC sandbox, and then check in
that symlink to put it under version control.

Note that in 3.0.1, you can only put symlinks in a Unix sandbox under
version control. In 4.0, you will be able to symlinks in a Windows
sandbox under version control.

Cheers,
Geoff

On 11/20/2011 11:38 AM, gsokhi wrote:

Does RTC has symlink capability like cleacase ie cleartool ln

Not quite. What I'm saying is that you create symlinks with your normal
operating system commands ... not by some RTC command. Then you can put
those symlinks under source control via the same commands in RTC that
you use to put files and directories under source control.

Cheers,
Geoff

On 11/21/2011 3:08 PM, gsokhi wrote:

Bit confused.
Are you saying with 3.0.1 symlink are only supported in UNIX via RTC
GUI and not RTC SCM CMD command line?


gmclemmwrote:
You cannot currently create symlinks from the RTC scm command line
tool.
You would just create symlinks in your RTC sandbox, and then check
in
that symlink to put it under version control.

Note that in 3.0.1, you can only put symlinks in a Unix sandbox
under
version control. In 4.0, you will be able to symlinks in a Windows

sandbox under version control.

Cheers,
Geoff

On 11/20/2011 11:38 AM, gsokhi wrote:
Does RTC has symlink capability like cleacase ie cleartool ln

Right i think i get it now. So will RTC display symlink created with operating system commands as Symlink in RTC once version control?

Not quite. What I'm saying is that you create symlinks with your normal
operating system commands ... not by some RTC command. Then you can put
those symlinks under source control via the same commands in RTC that
you use to put files and directories under source control.

Cheers,
Geoff

On 11/21/2011 3:08 PM, gsokhi wrote:

Bit confused.
Are you saying with 3.0.1 symlink are only supported in UNIX via RTC
GUI and not RTC SCM CMD command line?


gmclemmwrote:
You cannot currently create symlinks from the RTC scm command line
tool.
You would just create symlinks in your RTC sandbox, and then check
in
that symlink to put it under version control.

Note that in 3.0.1, you can only put symlinks in a Unix sandbox
under
version control. In 4.0, you will be able to symlinks in a Windows

sandbox under version control.

Cheers,
Geoff

On 11/20/2011 11:38 AM, gsokhi wrote:
Does RTC has symlink capability like cleacase ie cleartool ln

I'm not quite sure I followed the syntax of the question, but I'm pretty
sure the answer is "yes" (:-).

Cheers,
Geoff

On 11/22/2011 11:08 AM, gsokhi wrote:

Right i think i get it now. So will RTC display symlink created with
operating system commands as Symlink in RTC once version control?


gmclemmwrote:
Not quite. What I'm saying is that you create symlinks with your
normal
operating system commands ... not by some RTC command. Then you can
put
those symlinks under source control via the same commands in RTC
that
you use to put files and directories under source control.

Cheers,
Geoff

On 11/21/2011 3:08 PM, gsokhi wrote:
Bit confused.
Are you saying with 3.0.1 symlink are only supported in UNIX via
RTC
GUI and not RTC SCM CMD command line?


gmclemmwrote:
You cannot currently create symlinks from the RTC scm command line
tool.
You would just create symlinks in your RTC sandbox, and then check
in
that symlink to put it under version control.

Note that in 3.0.1, you can only put symlinks in a Unix sandbox
under
version control. In 4.0, you will be able to symlinks in a Windows

sandbox under version control.

Cheers,
Geoff

On 11/20/2011 11:38 AM, gsokhi wrote:
Does RTC has symlink capability like cleacase ie cleartool ln

I am having the similar issue. I have a couple of question:

1. I am importing the code from SVN to RTC. I used Windows client to import, it only imported the symlinks as plain text files. I am trying to run that from Redhat client, will that make any difference?

2. In my first import, after the import is done, I modified the files from plain text to link file, checked in and delivered. When I accept the change set from windows workspace, I got errors (they are kind of warning, but the message says there were errors). Is this really breaking the change set accepting?

3. I tried to load the code on windows and got the same error message. Since this code will be built on all the platforms, I need to make it downloadable from all the build servers, including Windows and Unix. Will this break the RTC build process on Windows build machine?

As indicated earlier in this thread, symbolic links in the Windows file
system are not supported by the current release of RTC. So I'd suggest
not trying to do anything with symbolic links in the Windows file system
until you upgrade to a version of RTC that supports them (i.e. the
release of RTC planned for June 2012). Until then, you should limit
your usage of RTC symbolic links to Unix clients.

Note that RTC symbolic links that you create now with a Unix client
should be loadable into a Windows file system, after you upgrade to the
June 2012 RTC release.

Cheers,
Geoff

On 12/13/2011 3:23 PM, wyejazz wrote:

I am having the similar issue. I have a couple of question:

1. I am importing the code from SVN to RTC. I used Windows client to
import, it only imported the symlinks as plain text files. I am
trying to run that from Redhat client, will that make any
difference?

2. In my first import, after the import is done, I modified the files
from plain text to link file, checked in and delivered. When I accept
the change set from windows workspace, I got errors (they are kind of
warning, but the message says there were errors). Is this really
breaking the change set accepting?

3. I tried to load the code on windows and got the same error message.
Since this code will be built on all the platforms, I need to make it
downloadable from all the build servers, including Windows and Unix.
Will this break the RTC build process on Windows build machine?

I've imported an SVN dump (from Linux) using Win7 RTC client 4.0.0.1 and JTS 4.0.0.1.  Symlinks that were in the dump are imported, but lack the link attribute.  Is there a setting or different approach I should take, perhaps running the import on a linux client?