For the directory img/Interface, add the Subversion property svn:externals with the following value to make updates of your icons easy:

Code: Select all

Icons      http://svn.wowroster.net/interface/40x40/Icons
ItemSocketingFrame      http://svn.wowroster.net/interface/40x40/ItemSocketingFrame
PvPRankBadges   http://svn.wowroster.net/interface/40x40/PvPRankBadges
Spellbook       http://svn.wowroster.net/interface/64x64/Spellbook
TalentFrame     http://svn.wowroster.net/interface/40x40/TalentFrame

Put the above text in a temporary file. I call mine svn-externals (with a dash). Then use this command to set the property:

Code: Select all

cd img/Interface
svn propset svn:externals -F svn-externals .

I also add "svn-*" to my svn:ignore property so I can use that pattern for svn temporary files. For example, to see what I've changed, I do "svn diff > svn-diff" and load that in my editor. "svn log > svn-log" gives me a file with change comments. (This is driven by my using command line tools on a Linux box with a curses-based text editor. I don't have Tortoise or some other GUI-based Subversion client on the server.) When I want to commit with a multi-line comment, I edit svn-commit with the comment, then issue "svn commit -F svn-commit". (I could also use the VISUAL environment variable to select my editor for "svn commit" to spawn, but I share the login with a user who uses another editor, so I don't have that option.)

http://svnbook.red-bean.com/en/1.5/svn. ... rnals.html

The svn:externals property is sort of like a symbolic link. It causes a copy of the right hand size of each line to be checked out in the directory named in the first column. When you issue "svn update" in the parent directory, it issues a recursive "svn update" to each of the subdirectories.

This is most commonly used when you want to use a library from a different repository. You can also lock the specific revision you want by appending @123 (for r123, for example) to the end of the other repository's URI.

Note that "svn commit" does NOT recurse into the sub-projects. If you change something in one of the linked project's subdirectories, you'll need to issue a separate commit there.