[p4] Very big Perforce file : db.have

[Robert Cowham]

It exists already - it is called "p4 print"!

A perhaps more practical alternative is:

p4 sync 			(syncs whole client workspace)
p4 sync -k #0		("pretends" to sync whole workspace to zero rev,
i.e. remove files)

The latter command is the same as "p4 flush" in older releases. In this
instance it updates the db.have to remove all entries for the synced files,
and yet leaves the synced copies on disk. See command ref for more info.

Robert 

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
> Prakash Ranade
> Sent: 10 August 2006 23:53
> To: David Ferguson; jgrills at junctionpoint.com; Andres 
> Fuentes; perforce-user at perforce.com
> Subject: Re: [p4] Very big Perforce file : db.have
> 
> Hello Perforce Folks,
> 
> Speaking on the "db.have" file growth issue. 
> 
> Can we have a perforce command or argument in "p4 sync", 
> where perforce will not store the "the revision record" 
> synced to the client in the "db.have"?
> Let's say "p4 sync -a" to avoid tracking the "have-list" of 
> the client.
> 
> This could be very helpful in controlling the growth of the "db.have".
> Example, build system churns the build and store the 
> change/label information, but never interested to store the 
> "the revision record" of each files synced to the build client.
> 
> Regards,
>  
> Prakash Ranade