[darcs-users] recommendation for sub-projects with inter-mixed directories?

[Mark Stosberg]

Hello,

I'd like to describe a "use case" I have a for darcs, and see if other
users have a solution they like for it.

I would like to use darcs to manage complex website projects, which may
have several discreet sub projects. For example, a big site might have a 
"store", a "user database" and a "photo management tool". 

I think what's somewhat unique here is that in production, each project
needs to deposit some files in the same directories: 
    ./bin  
    ./config 
    ./www 
    ./perllib

Since these sub-projects are not related, I would like to manage them
separately. 

I can't just overlay them, because each would expect their own '_darcs'
directory to exist in the same place. 

Here's the best idea I've come up with to manage this, which I haven't
tried yet:

I could create another combined repository, which serve to collect the
contents of each sub-project in one place, and be used on the production
site for check-outs. 

If it turns out that some sub-projects do depend on the same files, I
could create another repo that just has 'shared' files that each
sub-project could pull from.

    Mark










-- 
--
 . . . . . . . . . . . . . . . . . . . . . . . . . . . 
   Mark Stosberg            Principal Developer  
   mark at summersault.com     Summersault, LLC     
   765-939-9301 ext 202     database driven websites
 . . . . . http://www.summersault.com/ . . . . . . . .