We are using our Perforce Workspace view to include other internal corporate "libraries" that means:
// depot / my / project / path / dev / ... // workspace_name / ... // depot / some / other / library / path / dev / ... // workspace_name / / ... We want to be able to specify that the included library should be synced with a specific label. I will not modify it, and want to make sure that new updates to that library do not break my code. In the context of GIT it will be called a subdomain.
// depot / my / project / path / dev / ... // workspace_name / ... // depot / some / other / library / path / dev /...@ Label_name // workspace_name / contains / ... but I get the following error:
Error Line Verification 2 of Field 'View' in the client specification Characters (@, #) are not allowed in '// Depot / some / other / library / path / dev /...@ label_name'
Is this possible?
It is not possible at present, currently in three ways I can see these handling:
1) Create a copy label that will set the desired version in your workspace, it is a bit weird, in which you have to make sure that you do not sync the set of files without reference to the label.
2) A common best practice for component-based development is that submodules are released. If that was the place, then you can just consume the version of your choice.
3) Create an import branch in which there is a version of the code that you want to use. You can still update it whenever you choose. This principle can theoretically give you control through minimal maintenance.
No comments:
Post a Comment