2 messages in com.perforce.perforce-user[p4] viewing p4 repository| From | Sent On | Attachments |
|---|---|---|
| akila_magesh | 18 Mar 2002 22:43 | |
| Jeff A. Bowles | 19 Mar 2002 00:19 |
| Subject: | [p4] viewing p4 repository |
|---|---|
| From: | Jeff A. Bowles (ja...@piccoloeng.com) |
| Date: | 03/19/2002 12:19:43 AM |
| List: | com.perforce.perforce-user |
At 12:14 PM 3/19/2002 +0530, you wrote:
I have been trying to use chora for viewing Perforce repository as p4web is a pain to use from the server side as an intranet product. Also doesnt let you customise.
The reason for looking at Chora being being that P4 repository also stores files in rcs format. However, I got stuck trying to display the log messages & user info of who checks in etc, as these info are being stored in P4 metadata files.
My advice: don't do this. It's not going to get you to what you want, in any reliable and supportable way, because the metadata is stored in a relational database and also because not all stored revisions are at the P4ROOT locations you'd expect from the //depot/blahblah pathnames.
Moreover, there's no guarantee *at all* that the revisions stored therein, will be stored in precisely the same way in the next release. None at all. It's a black box, for a reason.
(And that doesn't even go into the reverse engineering aspects of where you're headed, which is bad form for another software professional to get into.)
If you want a web access, and believe that p4web isn't it, then you can program your own. But you'll need to do it through the information portal that the Perforce server gives you to the data. If that portal isn't wide enough, bitch to Perforce to give you more information. SQL access, whatever.
But don't go down the path you're going at the moment. Not by pawing through P4ROOT. It's going to waste a lot of your time.
-Jeff Bowles Perforce Certified Partner, Trainer