Configurable target directories

[Stephen Lee]

Toby Johnson wrote:
>
> >> talking about a simple s/^$from/$to/ without needing to check whether
> >> the "from" grabbed an entire folder name or just part of one.
>
> Yes, that's what I had in mind. The "correct" path would be used for all
> internal use, such as renames and branches, and the path is only
> converted at the very end after the other determinations have been made.
> So it's really more of an operation on the dumpfile itself, than on the
> actual VSS paths.
>
Just to point out that this was essentially the same type of problem 
that my FilterOrphan.cpp ended up trying to solve... Like I said, .cpp 
was totally the wrong language to use for this, but I just had the tools 
already set up for it.

Having a suitable place where a config file could be supplied that 
allows a series of s/^$from/$to/ replacements to be done on the 
pathname, with parent folders created as needed, would make my program 
obsolete. (or perhaps s/$from/$to/ with the user usually providing the ^).

Initially I was only expecting to be replacing strings of the form 
"orphaned/_ABCDAAAA" in the dumpfile with a user-supplied string, but 
found there were a few other problems that needed fixing after a dumb 
search/replace, and a couple more problems created by the dumb fix to 
those. Most of the cascade of problems to fix would presumably be 
non-issues if done on the filename during dumpfile generation (it seems 
to "know" to create a parent folder at the right time etc.)

-- 
Stephen Lee <Stephen.Lee at hexagonmetrology.com>
Software Engineer, Vision Group - Pro-Measure Leader
Wilcox Associates Inc. (U.K.)