12 messages in com.perforce.perforce-user[p4] depot structure question| From | Sent On | Attachments |
|---|---|---|
| Lewit, Mike | 23 Feb 2005 09:58 | |
| Helck, Christopher | 23 Feb 2005 10:36 | |
| Stephen Vance | 23 Feb 2005 11:43 | |
| Lewit, Mike | 23 Feb 2005 12:11 | |
| Dave Lewis | 23 Feb 2005 12:11 | |
| Stephen Vance | 23 Feb 2005 13:17 | |
| Robert Cowham | 23 Feb 2005 14:36 | |
| Paul Goffin | 24 Feb 2005 01:42 | |
| Johan Nilsson | 24 Feb 2005 01:47 | |
| Lewit, Mike | 24 Feb 2005 09:11 | |
| jab | 24 Feb 2005 12:56 | |
| Lewit, Mike | 24 Feb 2005 13:57 |
| Subject: | [p4] depot structure question![]() |
|---|---|
| From: | Helck, Christopher (che...@ebs.com) |
| Date: | 02/23/2005 10:36:40 AM |
| List: | com.perforce.perforce-user |
I think the individual components are fine. It seems to me that the second part where you make a mega package is more of a build/release issue then a souce control issue. Could you just put a make file underneath proj/rel/1.1 that is smart enough to build the project from the component's depots?
It seems a shame to develop independent components and then to mush them together just to get a common version number.
Regards, C. Helck
-----Original Message----- From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Lewit, Mike Sent: Wednesday, February 23, 2005 12:59 PM To: 'perforce-user at perforce.com' Subject: [p4] depot structure question
I have a project with 3 components: CORE, JA & JB. I want to release each individually and release the entire system under one version#. I came up with the following structure for the project:
//products/proj/CORE/main .../CORE/rel .../rel/1.0 .../JA/main .../JA/rel .../rel/1.0
.../JB/main .../JB/rel .../rel/1.0 .../rel/1.1 .../proj/rel .../rel/1.0
.../1.0/CORE/1.0 .../1.0/JA/1.0 .../1.0/JB/1.0
.../rel/1.1 .../1.1/CORE/1.0 .../1.1/JA/1.0 .../1.1/JB/1.1
Project rel 1.0 is made up of core 1.0, JA 1.0 and JB 1.0. I rev'd JB to 1.1 and now released proj rel 1.1. Does this make sense? What would be the best way to create the ../project/rel tree? Do I manually branch each components rel tree into the .../proj/rel tree or do I sync everything to my build drive and then do a "Add to source control" to the .../project/rel tree?
Thanks, Mike
The information contained in this e-mail is confidential. This e-mail is
intended only for the stated addressee. If you are not an addressee, you must
not disclose, copy, circulate or in any other way use or rely on the information
contained in this e-mail. if you have received this e-mail in error, please
inform us immediately and delete it and all copies from your system.
EBS Dealing Resources International Limited. Registered address: 10 Paternoster
Square, London EC4M 7DY, United Kingdom. Registered number 2669861.
EBS Dealing Resources, Inc, registered in Delaware. Address: 535 Madison Avenue,
24th Floor, New York, NY 10022, USA, and One upper Pond road, Building F - Floor
3, Parsippany, NJ 07054, USA.
EBS Dealing Resources Japan Limited, a Japanese Corporation. Address: Asteer
Kayabacho Bldg, 6th Floor, 1-6-1, Shinkawa, Chuo-Ku, Tokyo 104-0033, Japan.




