Need hints for Repository structure

[Alan Boudreault]

Sorry Masklinn, I'm not sure to understand the following point:
"at the interface/ social level but none at the physical level"

Thanks,
Alan

On November 2, 2009 12:30:39 pm Masklinn wrote:
> On 2 Nov 2009, at 17:50 , Alan Boudreault wrote:
> > Does anyone could suggest me a better way to handle this kind of
> > company
> > repository. What structure do you use?
> 
> Not having a "company repository". Because in CVS or SVN you can
> checkout sub-repositories, and because setting up repositories tends
> to be painful/annoying, it's usually setup as a single huge repository
> for pretty much everything.
> 
> In most DVCS, it's the other way around: you can't really clone sub-
> repos and setting up repository is pretty easy (if not trivial), so
> people tend to setup repositories per project (or per feature using
> things like forests/subrepos at the project level).
> 
> Here, that's probably what I'd suggest as well: create a repository
> for each *project*, with some per-client grouping at the interface/
> social level if needed but none at the "physical" level.
> 

-- 
Alan Boudreault
Mapgears
http://www.mapgears.com