i guess it may be a better practice to
structure your project(s) in a way that
parts that not everybody should have,
are placed in a separate directory, and
not in the same tree. but of course it is
too late for your project now, this should
be done in the creation phase.
so that your dependencies are referenced as
something like this :
#include "../externals/subproject/header1.h"
instead of like this :
#include "subproject/header1.h"
2007/2/7, Adrian Broadhurst <adrian.broadhurst@vicon.com>:
> I have a problem / feature-request which other users may like to comment
> about.
>
>
>
> I am working using a very large SVN repository, which needs to be accessed
> remotely on a regular basis. Most users are only interested in part of the
> code base, although all code in the repository is active.
>
>
>
> Currently, it is possible to selectively check out individual directories,
> but keeping these all in sync manually is tedious and error prone. It
> would be very useful if a file 'EXCLUDE' could be placed in the .svn
> directory, of selective folders, so that in future those folders would be
> treated as if it had not been checked out.
>
>
>
> Are there any other ways of excluding directories?
>
>
>
> Any comments?
>
>
>
> Adrian Broadhurst
>
>
> ________________________________________________________________________
> This e-mail, and any attachment, is confidential. If you have received it
> in error, do not use or disclose the information in any way, notify me
> immediately, and please delete it from your system.
> ________________________________________________________________________
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 8 10:52:48 2007