headers
Robert Cowham | 1 Sep 2007 02:30
Picon

Re: [p4] Performance comparison between p4sql and p4 command

Behind the scenes p4sql translates SQL statements into p4 commands so there
is no real difference.

However, as a result, you can get yourself into trouble with injudicious
joins...

Robert

> -----Original Message-----
> From: perforce-user-bounces <at> perforce.com 
> [mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Greg Pan
> Sent: 31 August 2007 19:37
> To: perforce-user <at> perforce.com
> Subject: [p4] Performance comparison between p4sql and p4 command
> 
> Hi all,
> 
> I was wondering whether anyone has ever done a performance 
> comparison between executing a p4sql and p4 command, supposed 
> that both will give you the same (or very close) metadata. 
> For example for these 2 commands:
> 
>  
> 
> p4sql -s "select * from changes"
> 
> p4 cahnges //...
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jeff Grills | 1 Sep 2007 05:55

Re: [p4] Sharing workspace between 2 users?


I've had multiple users sharing a client/workspace on a conference room
machine before, and for the most part it worked well.  The one thing that
was a problem is that team leads had access to additional files that
non-leads didn't, which confused the syncing somewhat, or at least confused
the users doing the syncing.  You can help that significantly by limiting
the client's view to only the files that everyone can see.

j

-----Original Message-----
From: perforce-user-bounces <at> perforce.com
[mailto:perforce-user-bounces <at> perforce.com] On Behalf Of David Weintraub
Sent: Friday, August 31, 2007 5:00 PM
To: Geoff Rowland
Cc: Perforce User
Subject: Re: [p4] Sharing workspace between 2 users?

There is no problem with multiple users sharing the same client on the same
machine. Set your P4CONFIG environment variable to something like ".p4rc" or
"p4.rc" and put this file in the root of your client. This file will set the
name of the client, the user, etc. In fact, you may even want to setup a
special user with read only permission on the archive, and put this user in
a group with an extremely long login time. That way, no one has to log into
this client to use it.

I used a similar method to automatically install new revisions on our
servers. The servers each had a Perforce client that automatically sync'd
itself every few minutes. When we did a new release, we would put the files
out on the "production branch", and all of our servers would automatically
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tony Sweeney | 1 Sep 2007 15:26

Re: [p4] Sharing workspace between 2 users?

Geoff Rowland wrote:
> Is it possible to share one workspace between 2 different users?  Or
> maybe there is a better way of doing this:
> We have a machine in our conference room, which has different people
> using it.  Nothing is ever submitted from this machine, just latest
> builds pulled down from perforce.  
>   
OK so far.
> The problem is, different people may be using this machine - so even
> though the depot exists on disk, each person needs to create a new
> workspace when they login, which results in all the files being
> re-downloaded again, not just the ones that have been updated since the
> last person updated.
>   
Why is this part true?  What's forcing each person to create a new 
workspace when they log in to that machine?  You don't specify whether 
the conference room box (let's call it "Yalta") is Windows or UNIX, but 
either way it shouldn't be that hard to create a dedicated client spec 
for that machine, and have everyone use it anytime they log in to that 
box.  Naming the client spec for the machine is the Perforce default in 
any case.
> What is the best way to allow this (if at all)?
>   
Create a client spec for Yalta that reflects the parts of the depot of 
interest, where on Yalta's disks you want everything to go, and set up 
everyone's environment defaults such that when they log in to Yalta, 
this is the client spec that they all get.  The have list is per client 
spec, so with this set up there shouldn't be any unnecessary syncs just 
to get the latest stuff when someone new logs in.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jerry Bennett | 1 Sep 2007 21:18

[p4] HELP! need 2007.2/131374

Hello,

I was in the process of upgrading our perforce server, but lucky me they
JUST released a new version and of course my support license expired a week
ago.  If anyone has the perforce.exe from 8/21 aka 2007.2/131374, please let
me know so we can work out a way for you to get it to me.  I checked on the
perforce FTP site and they don't keep an archive of releases (stupid if you
ask me) so I'm hoping someone out there can help me get my p4 server back
online.

Thanks,

Jerry

_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 2 comments |
headers
Dave Lewis | 2 Sep 2007 00:20
Picon

Re: [p4] HELP! need 2007.2/131374

they do keep an archive of past versions, ftp.perforce.com, I think
you can just navigate to the dirs that have what you want.  also, I
thought once your license expired, you could not upgrade...  is it the
case you can upgrade to something that was released while the license
(actually, support license) was active?  I guess you'll find out!  let
me know if that works!

dave

On 9/1/07, Jerry Bennett <jerry <at> turtlerockstudios.com> wrote:
> Hello,
>
> I was in the process of upgrading our perforce server, but lucky me they
> JUST released a new version and of course my support license expired a week
> ago.  If anyone has the perforce.exe from 8/21 aka 2007.2/131374, please let
> me know so we can work out a way for you to get it to me.  I checked on the
> perforce FTP site and they don't keep an archive of releases (stupid if you
> ask me) so I'm hoping someone out there can help me get my p4 server back
> online.
>
> Thanks,
>
> Jerry
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user <at> perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jerry Bennett | 2 Sep 2007 00:27

Re: [p4] HELP! need 2007.2/131374

Actually, the overwrite the 2007.2 perforce.exe with the latest version.
That's the one I downloaded to start with.  And yes you can upgrade to the
latest version that was released while your support license was active.

-Jerry

-----Original Message-----
From: Dave Lewis [mailto:dlewis78731 <at> gmail.com] 
Sent: Saturday, September 01, 2007 3:20 PM
To: Jerry Bennett
Cc: perforce-user <at> perforce.com
Subject: Re: [p4] HELP! need 2007.2/131374

they do keep an archive of past versions, ftp.perforce.com, I think you can
just navigate to the dirs that have what you want.  also, I thought once
your license expired, you could not upgrade...  is it the case you can
upgrade to something that was released while the license (actually, support
license) was active?  I guess you'll find out!  let me know if that works!

dave

On 9/1/07, Jerry Bennett <jerry <at> turtlerockstudios.com> wrote:
> Hello,
>
> I was in the process of upgrading our perforce server, but lucky me 
> they JUST released a new version and of course my support license 
> expired a week ago.  If anyone has the perforce.exe from 8/21 aka 
> 2007.2/131374, please let me know so we can work out a way for you to 
> get it to me.  I checked on the perforce FTP site and they don't keep 
> an archive of releases (stupid if you ask me) so I'm hoping someone
(Continue reading)

Permalink | Reply | 0 comments |
headers
Qazwart | 2 Sep 2007 20:41
Picon
Gravatar

Re: [p4] Sharing workspace between 2 users?

The real problem is when the client spec is used on different  
machines and root drives. That is, someone is sharing the client on  
Machine "A" and Machine "B". It doesn't matter whether this is two  
different people, or the same person. This is trouble.

What we are talking about is a single directory workspace on a single  
machine that multiple users will access. The problem is the access to  
the workspace. Some Perforce user must own it, and it is best if  
everyone who used that workspace was that user (as you pointed out).  
Otherwise, there may be permission problems with user A sync'ing user  
B's workspace.

The best way is to use the P4CONFIG environment variable (which could  
be set in the Registry if this is a Windows machine to some file name  
(standards are .p4rc for Unix, p4.rc or _p4rc for Windows). Then have  
this file in the root of the client. This file will contain the name  
of the Perforce user, the workspace name, the P4PORT, etc. That way,  
if you go into this directory, you are automatically set to the  
correct user and port. I recommended that this be a special Perforce  
user with read only rights, and in a user group that has a very long  
log out time. That way, people who use this machine: Don't have to  
log in, and cannot -- even if they want to -- submit changes.

On Aug 31, 2007, at 6:00 PM, Gabor Maghera wrote:

> Although possible, sharing workspaces is a no-no according to best
> practices.  This may not be as much of an issue if you are not  
> submitting
> changes through it.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Neo Jia | 3 Sep 2007 08:20
Picon
Gravatar

[p4] How to use p4 windows version in cygwin?

Hi,

I am trying to use p4 windows version in cygwin. But I keeps getting
the following information when I am trying to sync with depot.

Path '/cygdrive/c\neo_tools' is not under client's root 'c:\neo_tools'.

Where I put 'c:\neo_tools' as my root in the client spec. file.

Thank you for your help and comments!

Neo

--

-- 
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 2 comments |
headers
G Barthelemy | 3 Sep 2007 11:20

Re: [p4] How to use p4 windows version in cygwin?

On 9/3/07, Neo Jia <neojia <at> gmail.com> wrote:
> Hi,
>
> I am trying to use p4 windows version in cygwin. But I keeps getting
> the following information when I am trying to sync with depot.
>
> Path '/cygdrive/c\neo_tools' is not under client's root 'c:\neo_tools'.
>
> Where I put 'c:\neo_tools' as my root in the client spec. file.

If using a bash shell, try aliasing p4 like this:
alias p4='p4 -d `cygpath -w $PWD` '
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 0 comments |
headers
Stephen Vance | 3 Sep 2007 14:51

Re: [p4] How to use p4 windows version in cygwin?

There is a cygwin build of p4 that handles paths better and is built 
against the cygwin libraries.

Steve

Neo Jia wrote:
> Hi,
>
> I am trying to use p4 windows version in cygwin. But I keeps getting
> the following information when I am trying to sync with depot.
>
> Path '/cygdrive/c\neo_tools' is not under client's root 'c:\neo_tools'.
>
> Where I put 'c:\neo_tools' as my root in the client spec. file.
>
> Thank you for your help and comments!
>
> Neo
>
>   

--

-- 
Stephen Vance
www.vance.com
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 0 comments |

Gmane