[p4] Problem about source tree orgnization.

[Weintraub, David]

Truth be told, symbolic links are officially supported on Windows 2000
and Windows XP too. However, this access wasn't built into Windows
Explorer or the Windows command line console. That means your programs
can create symbolic links, but people will have no way to access them
except through third party programs. For example, Perforce could build
into P4V and p4win the ability to create and access symbolic links, but
the p4 command line utility wouldn't be able to manipulate them.
 
After over a decade of support in the file system, MS finally will come
out with an OS that will be able to actually use this feature.
 
ClearCase on Windows does allow for the creation and manipulation of
symbolic link VOB objects via dynamic views. But then, ClearCase munges
the underlying OS and file system, so they're kind of cheating.

________________________________

	From: Shawn Hladky [mailto:p4shawn at gmail.com] 
	Sent: Wednesday, August 09, 2006 9:31 AM
	To: Weintraub, David
	Cc: Yan Tong; perforce-user at perforce.com
	Subject: Re: [p4] Problem about source tree orgnization.
	
	
	Windows Vista finally supports symbolic links.  A much overdue
feature!

	 
	On 8/9/06, Weintraub, David <david.weintraub at bofasecurities.com>
wrote: 

		Whoops! No attachment. I don't believe this list
supports binary
		attachments or formatted text.
		
		If you're on a *nix system (Unix, MacOSX, Linux)
Perforce supports
		symbolic links, and that would be the way to go. If
you're on Windows,
		life is much more difficult because Perforce on Windows
doesn't support
		symbolic links -- even if they were stored in Perforce
under *nix. 
		
		<rant>
		This is really rather stupid. Not Perforce, but Windows
OS. The
		underlying Windows file system, NTFS, supports file
names as long as
		32,000 characters, hard links, and symbolic links. In
fact, I believe 
		these are even implemented in the underlying Windows
API. However,
		Windows OS doesn't support these features!
		
		And, don't get me started about the VisualStudio IDE.
Or, its
		integration into *any* version control systems. 
		</rant>
		
		Maybe I should start drinking decaf.
		
		-----Original Message-----
		From: perforce-user-bounces at perforce.com
		[mailto: perforce-user-bounces at perforce.com
<mailto:perforce-user-bounces at perforce.com> ] On Behalf Of Yan Tong
		Sent: Wednesday, August 09, 2006 2:33 AM
		To: perforce-user at perforce.com
		Subject: [p4] Problem about source tree orgnization. 
		
		Hi,
		
		Now I have a depot named a, and the source tree looks
like (the attached
		image):
		
		
		*The problem:*
		
		The code in a->b->d->src->com is the same as the code in
		a->b->c->src->com, so I want to make a link between them
in order not to 
		maintain two copies of the same code.(Also only one
group is responsible
		for modifying the code, other groups just use them)
		
		
		
		What mechanism does perforce provide to support this
operation?? Can
		branch do this? 
		_______________________________________________
		perforce-user mailing list  -
perforce-user at perforce.com
	
http://maillist.perforce.com/mailman/listinfo/perforce-user