Showing posts with label Client. Show all posts
Showing posts with label Client. Show all posts

Monday, 6 December 2010

Alternate Perforce Client?

Can recommend a P4Win-like alternative for Perforce, hopefully that supports shelving and may be open source? Needn't be cross platform, just Windows would be fine.

I'm asking as I'm not a fan of the new P4V interface, and I found P4Win a lot more intuitive, easier to use, and much more stream lined.

I haven't found much in my Google searching, but I'm hoping this nexus of programmers might know of a hidden jewel out there. :)


View the original article here

Thursday, 25 November 2010

How can I work with multiple perforce client specs in TextMate?

I am using perfoce TextMate bundle to work with perforce from my TextMate editor. As far as I understood, you can only work with one client spec at a time. So I was wondering if anybody figured out a way to work with multiple client specs, without changing the P4CLIENT environment variable in TextMate.


View the original article here

Thursday, 11 November 2010

Perforce like client specs mappings with Mercurial

We recently moved from Perforce to Mercurial and love it!

One little problem: after much research we can't figure out how to map a special directory in the repository to some special place on the client. Here is an example of our hg repo:

/foo/source files/bar/source files/build /macosx/mac make files /win/windows make files

With Perforce, we were using client spec mappings to map //depot/build/macosx/... to just /build/... on the Mac client, and //depot/build/win/... to /build/... on the Windows dev box. Directories foo and bar are synced as is. Makefiles in /foo and /bar assume that our build makefiles are located in /build and we would like to keep them as is. The final client set of files should look like this:

/foo/source files/bar/source files/build/client specific make files

I've read about subrepos, but this solution does not seem to be client specific.

Any idea how to solve this problem will be very much appreciated!


View the original article here

Wednesday, 10 November 2010

How to get the last Perforce change list synced to a specific directory by non-local client spec (cmd line)?

I'm trying to return the last change list synced to a specific directory per client spec. I've researched this pretty heavily and am starting to think it's impossible. This is what I have so far:

p4 changes -m1 @

This will return the last change list synced to the passed in client spec, which I can then parse the CL out from. Example of output:

Change 798261 on 2010/11/08 by asdf@specname 'description...'

From that, I can easily parse out the change list: 798261.

What I'm trying to do is get similar output, but for a specific directory that's mapped in the client spec that's passed into the command. I know the -d flag usually lets you specify a directory in perforce commands, but p4 changes doesn't support the -d flag. This is what I'm going for if the -d flag was supported in p4 changes:

p4 changes -m1 -d /root/appname/bin/...@

In theory, if the -d flag was supported, this would return the last CL synced to /root/appname/bin through the passed in client spec. Is there any way to do this? Is there a p4 command I'm missing that would let me specify the directory and get the last CL synced to that directory? Any suggestions are greatly appreciated.

Thanks!


View the original article here

Friday, 5 November 2010

"Client can only be used from host" error

After getting a new PC, I am getting the following error when running commands:

Client 'workspace1' can only be used from host 'pc1'How can I fix this error?

The "Host:" field of the client workspace specification can be removed or changed to the new hostname. Please be aware that by default a client spec is tied to a client host. It is bad practice to share a workspace across client hosts.

The Host field can be changed by running the p4 client command from the command line. Or through P4V, go to View->Workspaces and edit the workspace in question.


View the original article here