Cooke, Mark
Mon, 15 Mar 2010 03:47:36 -0700
> > FYI: mod_python or mod_wsgi is not directly relevant to > > this problem. > > That was mainly to indicate which documentation I was > reading, in this case: > > http://trac.edgewall.org/wiki/TracModPython#Settingupmultipleprojects > > I was not sure this was the 'way to go'. I created a trac installation > per svn repository. This seems to work ok. > A lot depends on what you are starting from. We are converting from Visual SourceSafe, so have lots of legacy code jumbled up in a few archives. Part of our migration process is to review the archives and how related different projects are and how you control them. Then look at the 1-2-1 svn/trac relationship and group projects accordingly. My gut feeling is it is easier to combine repos than split them so go down the single repo route unless/until your needs dictate otherwise. > We are loosing the ability to report a bug across two projects > however. We'll see as we go if this is important or not. > If the projects are related such that you need to report across both, then why not use the same repo and one trac instance? Or, if it is a shared library, use the svn:external property from the 'consuming project' (that does not help with bug tracking specifically, though).
> Thanks anyway for your clarification, > -- No problems (and I am in no ways a guru, so YMMV as they say) ~ Mark C -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.