1 message in com.perforce.perforce-userShared files| From | Sent On | Attachments |
|---|---|---|
| Gile...@xeno.demon.co.uk | 02 Feb 1998 22:32 |
| Subject: | Shared files![]() |
|---|---|
| From: | Gile...@xeno.demon.co.uk (Gile...@xeno.demon.co.uk) |
| Date: | 02/02/1998 10:32:24 PM |
| List: | com.perforce.perforce-user |
If you have any UNIX machines, the easiest way would be to have the clients on the UNIX box with Samba providing the file sharing on the network. Samba is a freeware SMB server (i.e. it provides Microsoft network server protocols on non MS systems). You can use symbolic links to provide multiple paths etc. to files on the server. We do this to avoid having multiple source trees on UNIX, OS/2 and shortly NT. It also simplifies backup etc. Samba performs pretty well also.
Regards
Giles Davidson
-----------
From: Nick Triantos <nick at nvidia.com> To: perforce-user at perforce.com Subject: Shared files Date: 15 January 1998 18:01
Hi all,
My company is new to using Perforce, and most here are still using SourceSafe. People want to know how to get the equivalent functionality to SourceSafe's shared files. That is, one physical file which exists in two different places in a client mapping. For example, common headers between a library and an application should probably be shared.
I've thought about branching the file, but then we have the manual process (albeit an easy one) of integrating the file to its other location. Is there anyone who's already made some kind of a Perl script that does this as a daemon?
Or, even better, does anyone have any ideas how to further simplify this problem?
Thanks much, -Nick
---- Nick Triantos Nvidia Corporation phone: 408/617-4054 1226 Tiros Way email: mailto:nick at nvidia.com Sunnyvale, CA 94086 www: http://www.nvidia.com




