Comments on: Using Subversion with WordPress – Part 2: Maintaining Vendor Branches and Upgrading WP Core Files

By: largo

largo — Thu, 27 Oct 2011 11:27:19 +0000

I enjoy what you guys tend to be up too. This sort of clever work and exposure! Keep up the excellent works guys I’ve incorporated you guys to blogroll.

By: patrick

patrick — Thu, 14 Apr 2011 23:41:29 +0000

ben,

old files may indeed be left behind, but you can get the full discussion from the relevant section of the subversion book to which the author refers in the first article (part 1). That section is comprehensive and also provides links to some tools to deal with such problems. Alternatively, if you just want to know that they are no longer part of the repos, you can do an svn diff –summarize between your working copy and a current vendor export.

By: ben

ben — Fri, 07 Jan 2011 14:52:57 +0000

Nice article, but…in step 2 has some questions.

How about wordpress original source delete some files or directories?

Use cp -a, you will leave the deleted files or directories in your repositories, and never aware about their deletion.

Any good idea?

By: elran

elran — Tue, 27 Apr 2010 15:57:59 +0000

Hi Spencer,

we created the “current” folder automatically when we checked out a copy of the current vendor branch.

$ svn co http://svn.yourdomain.com/vendor/wordpress/current/

this creates the folder for you.
see “Part 1” for more details.

By: Spencer Hill

Spencer Hill — Mon, 26 Apr 2010 06:55:02 +0000

Hey man – looks like a great tutorial to hit the need right on the head, but you lost me in part two where you said: “cd current…” where did we create a folder called current?

By: gib

gib — Mon, 08 Feb 2010 07:34:55 +0000

fully agree with tunesmith,
what about a svn switch automattic/tags/2.9.1.1
inside vendor/wordpress/current ?
anyway very useful articles, thanks a lot !

By: tunesmith

tunesmith — Sat, 07 Nov 2009 02:28:38 +0000

It would be nicer to just pull over the wordpress update through a svn update, and then merge it into one’s own workspace. Is this possible? It just seems that that export/delete/copy process is something that subversion should be able to do.

The alternative is externals, but it requires wordpress being in its own directory, and wp-content screws that up.

By: elran

elran — Sun, 20 Apr 2008 18:09:03 +0000

no they won’t.

if you followed steps #5 and #6 from Part 1 and prepared your files correctly – all your custom plugins and themes should already be under version control at this point.

furthermore, you would be merging only the differences between 2 versions of WordPress (an upgrade of core files) – this has nothing to do with your custom plugins and themes.

By: mike

mike — Sat, 19 Apr 2008 22:24:48 +0000

what about all your custom plugins, themes, etc? those will be overwritten with these commands…