Project files in repository [closed]

Question

Is it common practice to keep project files (i.e. files other that source code files) in the version control repository?

Also, are these files checked in/out on a regular basis?

I always envisioned a SCC repository as 'clean' with only source code files.

How do you manage the non-source code files in a repository?

Take a Visual Studio solution, as an example. Would you "check-in" the entire Solution's directory to the SCCS or would you just add the source code files? What about when it comes time to build the Solution, then the entire solution needs to be checked out? Maybe it's best done with a manual process?

Answer 1

I think the general rule of thumb is that the minimal amount of data required to make the project compile and run should be included. That includes art (or other basic data files) and any build scripts. In the case of an autotools project, this usually means a configure.ac. In a Visual Studio project, it means the Visual Studio project file. But you wouldn't include anything that can be automatically generated from the rest, for example a "configure" script, if a configure.ac is already there.

CVS and Subversion both have flags for adding binary files (Subversion adds it automatically), which is great for things like images and project files (the binary ones, anyway). Subversion also allows for file locking, which can be good for artists who don't want to clobber each other's work.