[p4] UPDATE: mks, cvs2p4, perfmerge, and P4 2005.1

[Francis Joanis]

Hello everyone,

After exchanging some info with P4 support, I was able to get away with
the problems I had with perfmerge2.pl.

Here's the full story...

We wanted to convert our **old** MKS Source Integrity 7.3 archives to
Perforce. Since there was no direct MKS-P4 conversion tool, we had to
use some intermediate conversion scripts.

1) The si2cvs script was used to convert from MKS SI to CVS. You can
obtain the script here: https://sourceforge.net/projects/mks-si-to-cvs/

2) The cvs2p4 script was used to convert CVS RCS archives to a P4
checkpoint.

3) The perfmerge2.pl script was used to merge the converted checkpoint
with our P4 live server's checkpoint.

I had a lot of trouble at step #3... perfmerge2.pl was producing a weird
merged checkpoint where some files "shared" changelists and it also
produced a lot of warning messages such as the following when doing the
conversion process.

"Use of uninitialized value in concatenation (.) or string at
perfmerge2.pl line 301, <FH> line xxxx.
Use of uninitialized value in concatenation (.) or string at
perfmerge2.pl line 301, <FH> line xxxx.
Use of uninitialized value in concatenation (.) or string at
perfmerge2.pl line 301, <FH> line xxxx."...

P4 support, which I found, by the way, **amazing**, then sent me new
versions of the perfmerge2.pl and P4/Journal Perl lib.

It looks like using these new versions solved all my problems. I still
have to do it on my live server (I was testing the merge on a test
server), but I think it's going to be fine.

If any of you has questions, just drop me a line and I'll be glad to
help.

Thanks,
Francis Joanis