[p4] Newbie questions - David Birkhead - com.perforce.perforce-user

7 messages in com.perforce.perforce-user[p4] Newbie questions

From	Sent On	Attachments
joha...@esrange.ssc.se	07 May 2001 06:31
Chuck Karish	07 May 2001 07:48
David Birkhead	07 May 2001 07:59
Stephen Vance	07 May 2001 08:27
joha...@esrange.ssc.se	10 May 2001 00:02
Stephen Vance	10 May 2001 00:40
joha...@esrange.ssc.se	10 May 2001 04:17

Subject:	[p4] Newbie questions
From:	David Birkhead (dav...@PiccoloEng.com)
Date:	05/07/2001 07:59:40 AM
List:	com.perforce.perforce-user

At 03:31 PM 5/7/2001 +0200, johan.nilsson at esrange.ssc.se wrote:

Hi,

I'm currently trying out Perforce as a replacement for another SCM tool. I've read through lots of docs and read through the mailing list archives, but nevertheless have a few questions:

1) Is it possible to branch on a previously created label?

Yes, The simplest command line for this would look something like this: p4 integ //depot/main/... at LabelName //depot/NewBranch/...

I think I managed to do that by creating a branch and then initially run 'p4 integrate -b MyBranch -s @MyLabel', followed by resolve - correct?

Yes, Assuming that you have set up your branch spec correctly this will work. In the long run this is a better method of maintaining codelines.

2) Is there any whitepaper on how to share common components (3rd party/binary and in-house/source) between different projects?

Let's assume we're using UtilityX in all our projects. Version 1.0 of ProjA was released using UtilityX 1.0.1 and v2.0 of ProjB was released using UtilityX 1.2.12. I guess I could have different client specifications for each project, mapping UtilityX to my client using label specifications - but how will I communicate depedency changes to other developers (e.g. when we should begin to use UtilityX 1.2.12 in the new version of ProjA) - does everyone have to change their client settings? Should I use branching instead?

One approach is to include a 3rd party area in your project branches. Remember that as long as the files are not updated in the branch then they are a virtual copy and cost nothing in terms of disk space.

By using this approach each project/branch is self contained. This keeps your development environment much simpler and makes your build process much easier as well.

3) Is there anyone running the server on Win NT/2000 who's got automated backups running safely (no comments on NT vs *NIX please)?

I use a win2000 box for development, but do not have any win2k servers in production at the moment. I don't see win2k as a problem, I just haven't worked with a customer that needs/wants it.

For a good overview of backups and the like you might look at the FAQ on \ System Administration by Jeff Bowles. http://public.perforce.com/public/perforce/faq/admin.html

If so - do you have any sample batch files available? Are there any documentation available on possible error codes returned from 'p4 admin stop', 'p4d -jc', 'p4 -verify' etc ?

Hope this helps,

-Daveb

--------------------------------------------------------------------