Anthony Ettinger wrote:
> I've attached an image to try and visualize what I'd like to do with svn...
>
> Given the example:
> My vendor is: WordPress, I need to keep up to date with latest stable
> releases: 2.0.1, 2.0.2, etc.
>
> I'd like to customize a few things about WordPress in one location
> that I can use across all my sites: ie: modify some templates,
> features
>
> I still want to be able to customize on a site-by-site basis as
> well...ie: database.conf, environment.conf, logo.png, etc. etc.
1) Install SVK
2) Mirror WordPress's repository (`svk mirror`)
3) Create master local branch based off the mirror (`svk cp`)
3) Create local branches for each site off master local branch (`svk cp`)
4) Whenever WordPress cuts a new release, rebase your master local branch
5) Then rebase your site branches from your master branch
SVK makes this very easy to do (you will be running `svk pull` to get the
upstream changes during steps 4 & 5). SVK manages the merging for you in a very
automated way.
http://svk.bestpractical.com/
HTH
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-15 13:08:49 CET