Martin Furter wrote: >> http://svn.apache.org/viewvc/subversion/trunk/tools/client-side/svn-viewspec.py?view=markup >> > > No, I didn't know that script, it's nice. > > The only problem I see with that script is that it is a script. If it > were integrated into subversion all clients can (and probably will) > include the feature.
I wholeheartedly agree that this is functionality that belongs in Subversion itself. I can easily envision the likes of 'svn checkout --view VIEW-FILE' (where VIEW-FILE is a local path *or a Subversion-versioned file URL*). Some things stand in the way of this being of practical drop-in use today, though. First, Subversion still has a significant shortcoming in its sparse checkouts support that was pointed out to me recently (via the svnbook issue tracker, of all places): you cannot register your desire to exclude bits of a tree *at the time you check out the tree*. You can't say, "Gimme /trunk but without /trunk/massive-test-data-tree." You'd have to checkout the big ol' tree you don't want, and 'then' exclude the thing. Alternatively, you can try to build a tree piecemeal of the stuff you want -- but then if new stuff appears in the repository, you might not notice that stuff. Secondly, it's still limited to subsets of a particular repository tree. There's no support for assembling trees from various repository locations, or locations in other repositories, etc. Still, maybe we have enough from a rapid-prototyping standpoint now to start looking at getting some skeletal support for views into place? -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
