Either VIPM could limit the "backsave" to what is available in the LV-version that the package is developed for, or it could offer multi-stage backsaving as far back as there is installed LV dev versions.
I have made such a VI for backsaving several times as well, and it has to take into account that you don't want to drag with you anything from Program Files (user.lib, vi.lib etc.), it has to make sure that you end up in the proper directory for package building and such. It seems I have to take a new thing or two into account each time I do this "backsaving" VI, and/or I end up patching something anyway after that VI has run.
If such a feature was available in VIPM itself we wouldn't have to make these tools ourselves (obviously :-)).
I have made such a VI for backsaving several times as well, and it has to take into account that you don't want to drag with you anything from Program Files (user.lib, vi.lib etc.), it has to make sure that you end up in the proper directory for package building and such. It seems I have to take a new thing or two into account each time I do this "backsaving" VI, and/or I end up patching something anyway after that VI has run.
If such a feature was available in VIPM itself we wouldn't have to make these tools ourselves (obviously :-)).
/Steen