Posted on behalf of forum user 'UnstoppableDrew'.
[http://forums.perforce.com/index.php?app=forums&module=forums§ion=findpost&pid=14871]
JonY, on 2014/08/14 18:44:58 UTC, said:
> I'm considering migrating from SVN but I'm having a little trouble understanding what constitutes a workspace.
>
> If I have a depot with modular shared code used across all projects and another depot with project specific code + assets, can they both be checked out into the same workspace? Or would the shared libraries be checked out into one workspace and the project code / assets be checkout out into another?
>
> What about other projects? Could I use one workspace to juggle multiple projects? Thanks
>
Think of a workspace as your window into the source tree. Older SCMs like
Subversion tend to be all or nothing. You svn co some_project and you get
everything under some_project. With Perforce workspaces, you can define
specifically what stuff you want, in a variety of ways. To your question above,
you absolutely can create a single workspace that pulls in sources from one
depot, and assets from another.
Working with multiple projects generally is done with multiple workspaces. Kind
of depends on your exact setup, but for example, when I'm dealing with
multiple branches of a products source tree, say mainline, devproject_1,
devproject_2: I will have a workspace for each branch, that maps only the code
on that branch. This especially gets important as your code base grows.
--
Please click here to see the post in its original format:
http://forums.perforce.com/index.php?/topic/1635-perforce-free-20-users-20-workspaces-unlimited-files-server