getlabel and working folders

[bradw2k]

I do not understand why getlabel requires the -labelworkingfolder or -destpath to be specified. I want to be able to perform the getlabel operation and have Vault get at that label to all of the appropriate working folders that I have specified for the repositorypath *and its subfolders*. If I have to explicitly set -labelworkingfolder, this defeats the purpose of having working folder overrides set in the subdirectories ... it ends up getting code for those subdirectories to places that I don't want to get the code, which is wasteful, and then I have to perform *more* getlabel operations to get the subdirectories to their appropriate working folders.

Seems broken.

And I do not understand the answer here, it is not an explanation, it amounts to "that's the way it works":
http://support.sourcegear.com/viewtopic ... kingfolder

Is there a better workaround than doing a separate getlabel operation for each and every working folder?

[dan]

There probably isn't a good reason for why its done this way, and the workaround of doing multiple get labels is probably the best way to go.

I'll add this a change request - sorry for the inconvenience in the meantime