[p4] Mapping archive files to depot files

[Robert Cowham]

P4 fstat -Oc

Shows you lbrFile

C:\bruno_ws>p4 fstat -Oc //depot/jam/rel2.1/src/jam.c
... depotFile //depot/Jam/REL2.1/src/jam.c
... headAction branch
... headType text
... headTime 1106847349
... headRev 1
... headChange 749
... headModTime 1106847325
... lbrFile //depot/Jam/MAIN/src/jam.c
... lbrRev 1.16
... lbrType text

So the above file for REL2.1 refers to the MAIN version.

Have you checked out
http://public.perforce.com:8080/@md=d&cd=//guest/sven_erik_knop/p4bucket/&cd
f=//guest/sven_erik_knop/p4bucket/p4bucket.py&c=xJW@//guest/sven_erik_knop/p
4bucket/p4bucket.py?ac=22


Robert
www.vizim.com
The premier source of certified, independent Perforce consulting and
training

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Ed Swierk
> Sent: 11 July 2009 01:38
> To: perforce-user at perforce.com
> Subject: [p4] Mapping archive files to depot files
> 
> We use p4 to store generated binary files as well as source 
> files, and I am developing a process for archiving and 
> removing no-longer-needed files to free up disk space on the server.
> 
> I think I understand the dangers and tradeoffs of various 
> methods for removing archive files, including running p4 
> obliterate and removing the files directly without touching p4.
> 
> One thing I'm missing, however, is a way to determine which files in a
> p4 depot refer to a given archive file. Without this, I can't 
> see any way to know which file revisions need to be p4 
> obliterated to make an archive file disappear, or which file 
> revisions might be affected if I remove the file directly.
> 
> Surely p4 knows the answer, or it wouldn't be able to keep 
> track of lazy copies. Is there any way to extract this 
> information short of groveling through a database checkpoint file?
> 
> --Ed
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>