Reputation: 3
We're using a tool that is vital to create our projects which puts files all over it's filestructure. For instance
The code might be stored like so
Some associated setup files might be in another directory
It does this for a number of directories and it's a bit more nested than the simplified example above. These projects must have their files in these locations or else they can't be used.
We use a piece of software to run our projects on an external piece of kit and it requires this rather odd setup. The software can only be run from Windows.
What kind of source control system can handle this kind of layout? (My main experience is SVN so that's my reference point) Ideally we'd only want to checkout the projects that we're currently working on. It would be nice to view all files from a particular project tomorrow.
I could use SVN and put the root in SVN but then it's a little tiresome to pick out and checkout all these files associated with one project. I can't put the project into separate SVN repos because they can't be checked out into the same directory.
Any suggestions would be gratefully received!
Edit:
I think Symlinks are probably the way to go - thanks for the help!
Upvotes: 0
Views: 97
Reputation:
How about using symbolic links? For example, suppose I checkout the projects from svn into:
Then create symbolic links (I'm using *nix syntax here):
Does this get you what you need for this tool?
Upvotes: 1