You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Anthony Ettinger <an...@chovy.com> on 2008/02/15 07:45:22 UTC
customizing vendor drops for use on multiple projects
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.
Can someone help me run through the commands that are involved at each
stage (layer) ?
Thanks.
--
Anthony Ettinger
408-656-2473
http://anthony.ettinger.name
@pets = Pets.find_all_by_species('dog')
@pets.each do |dog| {
if dog.name == 'Farley'
dog.nick = 'Sir Barks-A-lot'
elsif dog.name == 'Bonita'
dog.nick = 'Princess Boo'
else
dog.nick = 'Doggie?'
end
}
Re: customizing vendor drops for use on multiple projects
Posted by John Peacock <jo...@havurah-software.org>.
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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org