Perforce replied to my email today providing me with the instructions for
upgrading the server. It is a relatively simple procedure with a lot of
considerations. I'll be reviewing the documentation for the next week or so
and will give everyone plenty of notice prior to attempting the procedure.
It's still a ways off. The most pressing consideration seems to be the
possibility of breaking the P4Win and OS/2 P4 clients. I'm having further
discussions with Perforce to fully understand this issue and explore
possible alternatives. There are a couple of things that would assist me
with this. First, I would like to determine a head count of OS/2 and eCS
developers. If you are in this camp, please reply to my subsequent Roll Call
post (send me an email directly, not to the newsgroup). Also, I would like
to better understand the ability of OS/2 and eCS to possibly run P4 or P4V
in an emulation window under 32-bit Windows XP/Vista/7 or under 32-bit Linux
2.6. This might be an option if we are unable to pick a server release that
supports all our clients. If you are using P4Win and/or the OS/2 P4 client,
please post the download links you are using on the Perforce website. I do
not have these links. I'm also trying to convince Perforce to directly
support OS/2 and eCS in an upcoming private release. This is all under
"Paul S. Person" wrote in message news:***@4ax.com...
On Tue, 8 May 2012 09:47:37 -0500, "Marty Stanquist"
Post by Marty Stanquist
I've submitted a request to Perforce this morning asking that they upgrade
our server. This will allow us to use the GUI client P4V. Since we have
numerous team members using OS/2 and eComStation, I asked for clarification
on the download links for these clients as well. I'll keep the group updated
as to Perforce's response and if there will be any downtime as a result.
I did some testing a while back, and, at least without requiring
passwords, both P4Win and the OS/2 client work with the latest
I was able to do things like: define the client & local depot, add
files to the server depot, synch with the server depot, and propagate
changes between the two client depots. The basic stuff needed to
contribute to Open Watcom.
Of course, these older clients can only use the features that were
available when they were built. But then, I don't expect they will be
used to do much more than that; an up-to-date client will surely be
the thing to use to manage an up-to-date server.
If you want, I can add passwords and verify that they will work. I can
also try any other test, provided it is specific enough; my knowledge
of Perforce is very limited.
"Nature must be explained in
her own terms through
the experience of our senses."