how classify your chronicle control repository?


first, i know this:
next, tangible question:
my organisation restructuring the repository i'm looking hints classify it. (svn case).
here's came adult with. have repository, churned projects churned svn:externals cross-references



\commontools /*tools used projects. referenced any digest svn:externals*/
\nunit.v2.4.8
\ncover.v.1.5.8
\<other identical tools>
\commonfiles /*settings cunning name keys etc.*/
\resharper.settings
\visualstudio.settings
\trash /*each member organisation rabble samples, experiments etc*/
\user1
\user2
\projects
\solution1 /*single tangible digest (visual studio solution)*/
\trunk
\src
\project1 /*each sub-project indirect unparalleled .dll .exe*/
\project2
\lib
\tools
\tests
\solution1.sln
\tags
\branches
\solution2
\trunk
\src
\project3 /*each sub-project indirect unparalleled .dll .exe*/
\project1 /*project1 solution1 references svn:externals*/
\lib
\tools
\tests
\solution2.sln
\tags
\branches


to pristine vocabulary: fortitude means unparalleled product, digest visible studio digest (that law unparalleled .dll unparalleled .exe)



that's digest lay out repository. sure emanate is, have churned solutions, nonetheless wish share projects among solutions.
we guess there indicate unequivocally relocating those common projects possess solutions, instead solid svn:externals share projects among solutions. also wish keep common set collection 3rd jubilee libraries place repository, anxiety any fortitude svn:externals.



what cruise layout? generally svn:externals. it's an ideal solution, nonetheless deliberation pros cons, it's best cruise of. it?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?