On Thu, Apr 29, 2010 at 5:14 PM, David Bartmess <dingod...@edingo.net> wrote: > Thanks, that explains what I needed to know... Relative paths using a parent > (..) or absolute paths aren't handled. So it won't work with my system, > since all the build files point to a parent "sandbox" directory, not the > current directory, for the dependencies...
You can use relative paths, but they are relative to the repository. For example if I had a directory at svn://repos/foo/bar/barfoo and it had svn:externals = ../foobar, it would be referring to svn://repos/foo/bar/foobar. Maybe you should read up on the book a bit. It sounds like you're confused about what svn:externals do. They check out a repository directory that is located elsewhere in the repository into your current working directory. Let's take the above project. It would checkout in your working directory the directory svn://repos/foo/bar/foobar under directory barfoo in your working directory. What it sounds like you have is a build issue. That is, you have your build referring to code that is not in your current working directory, but happens to be located in a parent directory. That has nothing to do with the svn:external property. -- David Weintraub qazw...@gmail.com
