[p4] Is there a way to check out a file but not get a local copy?

Rick Macdonald rickmacd at shaw.ca
Mon Feb 26 21:05:32 PST 2007


If the release folder in the depot is already sync'd to disk, then 
Perforce will just change the permissions of the file on disk, thinking 
that it's the same as what's in the depot. So, it already does what you 
want.  You just submit it at the end.

I'd look at opening the file for edit _before_ over writing it during 
the build process. If the file is read-only, the write may fail anyway.

The above is for UNIX; I don't use Windows much. Hopefully it's the same.

...RickM...

Eramo, Mark wrote:
> I have a question in regards to p4add
>
>  
>
> Is there a way to Check a File out from the Perforce repository but not
> actually get a local copy? I see there is a -n option but that looks
> like a preview option and might not actually do anything.
>
>  
>
> The reason I need to do this is our build process builds a new jar and
> drops it into the release folder. We will then call Perforce to checkout
> what is in that folder in the repository without getting a local copy
> then submitting the new copy in the release folder to the repository.
>
>  
>
> I could modify the build process but I figured if I can save time with a
> flag to prevent a local copy from being put down, that would be easier
> for now.
>
>  
>
> Regards,
>
>  
>
> Mark
>
>  
>
>  
>
> _______________________________________________
> 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