I agree with Ximon. Again, not knowing anything about the feature
other than what Ben mentioned...having to explicitly specify
directories to check out will either a) be used only for very trivial
and temporary filtering, or b) be something that would be utilized by
a wrapper mechanism that would somehow create on the fly the list of
directories to check out based on external criteria (often utilizing
The property based filtering I propose seems to me to be a more
powerful, and yet also simpler and more elegant a solution. It would
be capable of doing complex filtering without the need to write
external tools. The name-based mechanism could even be folded into
the --filter mechanism by having a "meta property" that specified the
object's name or path, thereby allowing queries on names as well.
Per Ben's suggestion, I'm going to try to speak with Ben Reser about
> > Somebody is currently working on making 'svn checkout --
> > work as expected, and then creating a UI for explicitly including or
> > excluding subdirectories as needed. That would solve the same
> > wouldn't it?
> I think it would solve the problem, but in a less useful way. Let
> me see if
> you agree with my thinking.
> With the proposal for --filter all that the client performing the
> needs to know is that they want a mac osx version for instance.
> With the solution you refer to isn't it true that the client would
> need to
> fully specify the set of directories to include and exclude, and that
> therefore introduces potential for checking out the wrong set of
> for a given platform?
> If the 'UI for explicitly...' allows the client to pull the set of
> from a subversion property somehow then that would be closer to
> what Steve
> Johnson asked for but would not indicate what the directory set is
> for whereas
> the simple property 'arch=i386' requires less knowledge of the
> contents and labels the directory/file set into the bargain.
> Hmmm, just realised. The non recursive UI solution could work if it
> means that
> the set of directories/files could be specified by a script and the
> run the script or reference a file containing the required paths,
> and the
> file/script came from the repository and was named something like
> or mac_osx.paths or some such.
> To unsubscribe, e-mail: email@example.com
> For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Sep 9 02:29:19 2005