[p4] P4V vs. P4WIN
yariv.sheizaf at sap.com
Sun Apr 15 23:35:24 PDT 2007
SAP - SBS Cyprus Engineering Services TL
From: David Weintraub [mailto:qazwart at gmail.com]
Sent: ב, אפריל 16, 2007 2:28
To: Sheizaf, Yariv
Cc: perforce-user at perforce.com
Subject: Re: [p4] P4V vs. P4WIN
But what you were saying was for Unix users to use P4win. Yes, if you
can find a shared workspace between a Windows and Unix/Linux machine,
you could use the "AltRoot" (and remove the Host field) in order to
share a workspace between a Windows box and a Unix box. I do that
right now with the Cygwin version of "p4" on my Windows machine.
>> Pure Linux (or Unix or Mac) users working with P4V. Typically, People who have a mixed environment (and have a good knowledge of both interfaces) works with P4WIN (I must say, it was in objection to my recommendation to use P4V for Unix/Linux clients - but they chose the complex way of p4win/altroot).
However, what it sounds like you're saying is that if I have to do
something in Perforce and I am on my Linux box, I should leave my
Linux box, go back to my Windows box in order to use P4win and not
P4V, do whatever I needed to do, then go back to my Linux box to do
whatever I was doing in the first place.
>> As I wrote above - no. 100% Unix users should use P4V.
I can understand a Window only environment and standardizing on P4win,
but if you have a mixed environment, P4V may be the better choice
since it works the same on all platforms.
Most of the problems P4win people are having with P4V has to do with a
different interface and the different way you would use that
interface. When P4V first came out, there was a lot of short comings
with it, but over time, it has become more stable. more powerful, and
more useful. In my situation, where I work on both Windows and
non-Windows system, I am better off using P4V which gives me a single
interface on all the various systems I may use.
>> I agree that P4V stability and performance is now much better that 4 or 5 releases ago (even not similar to P4WIN). And, again, for pure Unix environment it is the straight direction to use it.
The main problem is the intuitivity, and this factor can be a real mine when try to sell (or "internal corporate sell") of the Perforce product, specially to users who are Windows-dedicated or people who used competitor nice CM tools GUIs.
On 4/15/07, Sheizaf, Yariv <yariv.sheizaf at sap.com> wrote:
> Hi David,
> Answer your technical question:
> > Unix oriented users install P4win on their PCs, use the AltRoot option
> > and work from P4win because P4V UI is problematic.
> Explain how I install P4win on my Linux box again? The biggest
> advantage to P4V is that it works on *all* platforms while p4win only
> works on Windows. Using P4V means that I use Perforce the same way
> whether I am on my Linux box or on my Windows box.
> >> If your Perforce client work space is located on a filer (Network
> Appliance or alike), or using Samba, you can see your client files in
> both Linux and Windows, and use P4win (or P4v) from Windows using
> AltRoot field in your client spec setting.
> Yariv Sheizaf
qazwart at gmail.com
More information about the perforce-user