version control - What is the right way to structure a large multi-application codebase in SVN -


we've got single repo codesion, http://john.svn.cvsdude.com, single svn project http://john.svn.cvsdude.com/myproject, contains few subdirs individual visual c++ solutions

this started 1 application , though did split off separate library projects future re-use, it's still same svn project. lets aim have multiple applications overlap in libraries used, what's right/best way set in svn? of course 1 keep 1 svn project , put app-projects , library-projects sub-dirs, hardly seems right somehow.

say have app1, app2, app3 , librarya, libraryb, libraryc, libraryd these separate projects/solutions... how organise under 1 (or more repos)? there best-practice?

i keep everything in one repository , put each project and library in separate root directory of repository (see planning repository organization details).

keep in mind repository structure do not have to identical project files structure on disk.

also use svn-externals share library directories (kept separate root folders of repository) among various projects.


Comments

Popular posts from this blog

ASP.NET/SQL find the element ID and update database -

jquery - appear modal windows bottom -

c++ - Compiling static TagLib 1.6.3 libraries for Windows -