>
> Well, after trying various approaches, I discovered the
> svn:externals property. This seemed promising, so I tried the
> following:
>
> 1. create a new SVN project with just the client-specific
> directories -- i.e., the Rails directories that contain files that
> will be modified for a specific client. These include public/ and
> config/ at the moment.
>
> 2. use svn:externals to link the rest of the directories from the
> main trunk to the client project: app/, components/, etc.
>
> After an svn update, I had all the files I needed in the client
> directory.
>
> I haven't had time to modify the Capistrano deploy file so I have
> no idea how this svn:external thing will work on deployment. I'm
> hoping that SVN will 'magically' download both the client-specific
> and external files from the main project.
>
> However, my brain is too fried to tackle that today. Tomorrow is
> another day!
>
In case anyone else ever runs into this problem (no one currently on
the list apparently cares!), I can confirm that, yes, indeed, using
svn:externals solves this problem. It worked with a Capistrano
deployment, with no problem.
Now, I just need to remember NOT to edit those external files
(already done it once, already.) I need to figure out how to check
them out read-only.
-- John
Received on 2008-02-21 22:34:37 CET