default project structure

Hello,    We routinely create svn projects that have the same initial file structure (8 or so top level directories, an sql directory with some scripts in it, etc).    We would like to:    - have the default project be it's own svn project (because we make enhancements / changes from time to time and would like the default project to be under version control)    - use the default project as a starting point for new svn projects    Right now, if I checkout the default project, and just import it as a new project, then when I make commits they commit back to the default project instead of the new project.    Maybe I should manually remove the .svn files after checking out the default project, before importing to the new project?    I appreciate any help steering us in the right direction on this.    Much thanks!  -Ben

Last updated 12 years ago

Hi Ben    Your plan (version the default project) sounds sensible. My recommendation would be to *branch* from the default project, e.g. assuming you have your default project at, say, http://example.com/svn/trunk/default you'd execute:svn copy http://example.com/svn/trunk/default http://example.com/svn/trunk/new_project -m "Creating new project"That way you'll simply need to check out the new project without worrying about abusing an existing working copy ;-)    Cheers  John

Remember what should be remembered, and forget what should be forgotten.Alter what is changeable, and accept what is mutable.