[p4] P4V vs. P4WIN

[Ivey, William]

> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com]On Behalf Of David 
> Weintraub
> 
> > 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?

You don't. But you can still use it to manage files on a
shared filesystem. I work with four flavors of Unix, but
all have the same filesystem mapped, as does Windows,
so I could manage everthing using nothing but Windows tools.
Not saying that's the best way, but there it is. (Only about
5% of the people here are really comfortable on Unix systems,
so Windows is their primary system.)

> Perforce also removed P4win from the standard Windows Perforce
> installation. If you want to use P4win, you have to install it
> separately. This shows the direction Perforce wants to head in the
> future.

Actually, I think it shows the desire to keep the packages
a reasonable size. P4V is also in its own install package now.

> I guess I am old fashion in this respect, but I somehow expect that
> developers have the technical expertise to understand the tools they
> are using.

I've found some very resistent to learning tools that are not within
what they perceive as their core job responsibility - I've seen
developers who will stay  up all night learning the latest Java tech
or tool but who still can't use a command line on any system. (I've
seen developers who've never once opened a command prompt on Windows,
or who didn't realize that the ls command in Unix could be given a
path.)

-Wm