Russell Bryant wrote:
While svn:externals is certainly handy, it's something to only use where it makes sense. If a certain set of externals is primarily developed elsewhere, then it probably does make sense to use it. But, it comes down to depending on one of two factors:
- You don't maintain any changes that aren't made in the upstream repository.
or
- You are able to have your own branch in the upstream repository to maintain
your changes.
If neither 1 or 2 is true, then svn:externals does not make sense.
3) the "upstream repository" can really be the same repository. you can use svn:extenals to re-organize a part of the repository to fit your special needs (e.g. have a flat hierarchy for easy-built in pd-extended)
(you can also do this with "symlinks" (on an svn-level), but i think this makes things more complicated (e.g. you must have checked out the entire tree on filesystems that support symlinks))
mfg.sdr IOhannes