8 messages in com.perforce.perforce-userCommon Usage Patterns
FromSent OnAttachments
Robe...@SCRAP.de30 Sep 1997 00:38 
Robe...@SCRAP.de30 Sep 1997 05:49 
Brad...@email.mot.comBrad_Appleton-GBDA00130 Sep 1997 11:01 
Brad...@email.mot.comBrad_Appleton-GBDA00130 Sep 1997 12:09 
Robe...@SCRAP.de01 Oct 1997 00:57 
Brad...@email.mot.comBrad_Appleton-GBDA00101 Oct 1997 08:46 
Davi...@world.std.com06 Oct 1997 08:43 
Brad...@email.mot.comBrad_Appleton-GBDA00106 Oct 1997 17:37 
Subject:Common Usage Patterns
From:Robe...@SCRAP.de (Robe@SCRAP.de)
Date:09/30/1997 12:38:00 AM
List:com.perforce.perforce-user

Hi,

what's the best way to handle the following situation:

We are using several 3rd party libraries for which we have the source-code. I do install the stuff and make some changes until I can compile it, after this I check-in all the files. When we now get a new version I have to do the following steps:

0. Check out all the old files. This makes sometimes a lot of problems as Perforce gives an error: file(s) not on client. But the file is there, didn't move etc. I don't know why this error message comes?

1. Find out which files are no longer present in the actual distribution.

2. Find out if there are new files which are not allready in the depot.

3. Find out which of the files did change and check them in.

What's the best way to do this? I have some problems with this.

Robert M. Muench SCRAP EDV-Anlagen GmbH, Karlsruhe, Germany

==> Private e-mail: r.m.muench at ieee.org <== ==> ask for PGP public-key <==

When do you want to reboot today?