Taking a backup just doesn't seem like a practical code-sharing mechanism to me. Restoring from a backup wipes out the existing environment and establishes a new one. If I'm working on multiple projects and someone sends me a backup of their environment I can't afford to restore it and wipe out my existing environment. Yeah, I could save the old and restore it back later but that all seems overkill and makes it hard to share things. Selective exporting/importing of DAR files seems the appropriate way to save and share sets of workflows, cmds, etc. And it works fine ... I'd just like to clean up the issue that I may have to build 3 or 4 DAR files to share my complete WFA package.
I had some time today to test merging by: 1) do a pair of WFA exports, 2) rename files .dar to .zip, 3) unpack them, 4) combine the files in them, and then see if that could be 5) re-zipped and 6) re-named to .dar ... and then 7) imported into WFA. It turns out I can't even get a simple unzip and re-zip of a DAR file to re-import. I keep getting the error: Incompatible DAR - no upgrade path were found. DAR version 'null', installed version '2.1.0.70.32' when attempting to import.
It's as if WFA it can't detect the version of WFA the DAR was created by (i.e.; 'null') at the time of import. Does anyone have ideas what I might be overlooking or doing wrong? I first attempted the un-zip & re-zip using the Mac OS X built-in uncompress and compress functions. When that didn't work switched to Windows-7 and a free WinZip download. Neither worked. Anyone else unpacked and repacked a .dar file and gotten it to import? If so, what tools/environment were used?