p4v 获取文件可写
Perforce 正在将文件下载到连接到我的 MacBookPro 的可写外部硬盘驱动器（“777”）。就好像我的工作区中设置了“allwrite”选项，但事实并非如此。
我认为 Perforce 应该将文件标记为只读，直到我检查它们。有什么地方我错过了吗？
修订版 P4V/MACOSX104U/2009.2/236331 MacBookPro OSX 10.5.8
Perforce is downloading files to the external hard-drive connected to my MacBookPro as writable ("777"). It's as if the "allwrite" option is set in my workspace, but it's not.
I thought Perforce was supposed to mark the files read-only until I check them out. Is there a setting somewhere I missed?
Rev. P4V/MACOSX104U/2009.2/236331
MacBookPro OSX 10.5.8
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您的外置硬盘格式化为 hfs+ 吗？如果是FAT32，无论如何都是777。
Is your external hard-drive formated as hfs+? If it's FAT32, it will be 777 anyway.
您是否检查过 Windows 是否认为文件仅在与 Mac 客户端同步后才能读取？
Perforce 不喜欢从两个不同的工作区访问同一磁盘位置，也不喜欢从两个不同的主机访问同一工作区。这是因为服务器跟踪客户端上文件的状态；您正在乞求您的本地商店与仓库失去同步。
你真正想在这里完成什么？
我建议您忘记 FAT32；将 Windows 工作区放在 NTFS 卷上，将 Mac 工作区放在 HFS+ 卷上。提交&同步以共享数据。存储很便宜。
Have you checked if Windows thinks the files are read only after syncing with the Mac client?
Perforce does not like it when you access the same disk location from two different workspaces, nor the same workspace from two different hosts. This is because the server tracks the state of the files on the client; you're begging for your local store to lose synchronization with the depot.
What are you really trying to accomplish here?
I would recommend that you forget about FAT32; put your Windows workspace on an NTFS volume and your Mac workspace on an HFS+ volume. Submit & sync to share the data. Storage is cheap.