Externals-only module in SVN (was Re: Proposal for change to repository governance - follow-on)

Colin Clark colin.clark at utoronto.ca
Tue Aug 18 19:49:15 UTC 2009

HI All,

A couple months ago, Antranig made this suggestion for creating a  
externals-only module of our SVN repository that pulls together all of  
the separate Fluid code bases into a single directory structure. This  
will help solve the problem many of us face where we end up getting  
multiple checkouts of Infusion all over the place.

People generally thought it was a good approach, and I do too. I'm  
going to go ahead and implement this as follows:

     engage/    -> http://source.fluidproject.org/svn/incubator/engage-client/
     kettle/        -> http://source.fluidproject.org/svn/incubator/engage-sketches/trunk/ 
  (this should probably be renamed soon)
     infusion/    -> http://source.fluidproject.org/svn/fluid/infusion/


On 12-Jun-09, at 4:44 PM, Antranig Basman wrote:
> As a follow-on proposal, I would like to talk about strategies for  
> working across our
> various projects. Those working on engage need also to work on  
> infusion - and also
> working with a trunk version, in case they need to make commits to  
> base functions.
> To be clearer - it would be great for the team that works across  
> multiple projects to
> be able to do this with a SINGLE checkout of each project. Our  
> traditional solution
> based on externals is asymmetric - and ends up with multiple images  
> of infusion.
> My proposal is to make an "externals-only" section which is intended  
> to be the root
> checkout for developers who work across multiple trunks. This  
> ensures that multiple
> projects can be checked out with consistent directory names and in a  
> consistent
> relative structure.
> I suggest making an area such as "fluid-checkout" or "fluid- 
> externals", which,
> for example, has an externals structure like this:
> fluid-checkout\
>   fluid-infusion -> https://source.fluidproject.org/svn/fluid/infusion/trunk
>   fluid-engage -> https://source.fluidproject.org/svn/fluid/engage/trunk
> and any other projects that we might work with.

Colin Clark
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto

More information about the fluid-work mailing list