[p4] p4 *nix to p4 win

Zoltan Grose zgrose at mac.com
Fri Oct 7 10:18:39 PDT 2005


I see. So P4 wouldn't be able to un-delta my source unless I convert  
all the ,v files to the platform's native line-endings. Is that a  
good summary?
-z

On Oct 7, 2005, at 10:14 AM, Jeff Grills wrote:

>
> No, the metadata is all in the db.* files, or the checkpoint which  
> you will
> restore on the new platform.  The *,v files are the delta-stored  
> archive
> files.
>
> j
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Zoltan Grose
> Sent: Friday, October 07, 2005 10:42 AM
> To: perforce-user at perforce.com
> Subject: Re: [p4] p4 *nix to p4 win
>
> Ah, the line ending issue is for Perforce itself (e.g. its metadata)?
> -z
>
> On Oct 7, 2005, at 3:45 AM, Robert Cowham wrote:
>
>
>> Translate the line endings on all ,v files in the repository from
>> \n to \r\n
>> if going to Windows, and vice versa as per the Tech Note 10.
>>
>> Run the following command from the target $P4ROOT directory:
>>
>>     find . -type f -name '*,v' -print0 | xargs -0 perl -p -i -e 's/
>> \r\n/\n/'
>>
>> The command syntax might be different depending on the specific
>> platform and
>> shell that you are using. For example, on Solaris, the equivalent
>> command
>> is:
>>
>>     find . -type f -name '*,v' -exec perl -p -i -e 's/\r\n/\n/'  
>> "{}"\;
>>
>> Make sure by testing your conversion on some files that the above
>> is going
>> to work properly before you do it!! I have blythely used unix2dos  
>> that
>> seemed to be available and yet didn't change the file in place!
>>
>> Robert
>>
>>
>>
>>> -----Original Message-----
>>> From: perforce-user-bounces at perforce.com
>>> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Zoltan  
>>> Grose
>>> Sent: 06 October 2005 23:11
>>> To: perforce-user at perforce.com
>>> Subject: Re: [p4] p4 *nix to p4 win
>>>
>>> I retract part of my original statement. My OSX is formatted
>>> as case- insensitive so it is even doubly less of an issue
>>> than I originally thought. =)
>>>
>>> So know the only question mark is the line endings.
>>>
>>> -z
>>>
>>> On Oct 6, 2005, at 1:36 PM, Jeff A. Bowles wrote:
>>>
>>>
>>>
>>>>
>>>> On Oct 6, 2005, at 10:13 AM, Zoltan Grose wrote:
>>>>
>>>>
>>>>
>>>>
>>>>> So I'm getting a brand spanking new box in the next few
>>>>>
>>>>>
>>> weeks and I'm
>>>
>>>
>>>>> thinking of moving my depot over. Right now I run my
>>>>>
>>>>>
>>> server on an OS
>>>
>>>
>>>>> X box and the new server would be Windows. I'm going from case
>>>>> sensitive to case insensitive so there shouldn't be any
>>>>>
>>>>>
>>> issues there.
>>>
>>>
>>>>> Any other gotchas you guys can think of? We are a micro-deployment
>>>>> (200 MB depot, 5 users) and the IP address will remain the same so
>>>>> client migration is N/A.
>>>>>
>>>>>
>>>>>
>>>>
>>>>     There shouldn't be many issues.  I would install VNC or
>>>>
>>>>
>>> a similar
>>>
>>>
>>>> "virtual console" application on the Windows machine to ease
>>>> administration.
>>>>
>>>>     (Obviously, you're going to use the tech notes info for
>>>>
>>>>
>>> converting
>>>
>>>
>>>> between platform types, right?)
>>>>
>>>>     -Jeff Bowles
>>>>
>>>>     ps. Why change platform types?
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> 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
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>




More information about the perforce-user mailing list