On 01/03/2012 4:47 PM, Pietro Moras wrote: > > Hi, > > Having to develop two distinct, un-related Projects, I wonder > whether it is sensible to store them both into a unique Subversion > Repository, or it is natural to create two distinct Repositories, each > one dedicated to a unique Project. > > > In other words, a Subversion Repository is naturally meant for more > than one, unrelated, independently versioned project, or not? > > Thanks. Yours, > - P.M. > > > > _______________________________________________ > Eric mailing list > [email protected] > http://www.riverbankcomputing.com/mailman/listinfo/eric In general I would take the approach that one project = one repository, is eases things like ticketing, etc., but if there is code in common you might like to consider a third repository for common code, (accessed by externs in the respective project specific repositories). Such a set up is far easier to run. If both projects are released as a single package you might also like to consider a master, release project with things like package build scripts, documentation, etc., in. In this case you will probably end up with a top level package with extern references to two, or more, project repositories, each with possibly extern links to a common repository.
I know of a number of commercial packages using subversion that use a similar structure. Gadget/Steve
_______________________________________________ Eric mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/eric
