Vpack link doesn't check for older versions correctly

[sunep]

I ended up with two folders: vvvv-Message_x64 and vvvv-Message Shouldn't the vpack file check for older versions installed, even though the name is different?

[velcrome]

Could it be that the old folder vvvv-Message_x64 comes from a quite old install (back from the days without vpm, when there was not just a single anycpu distro)? vpack files might have the power to do what you ask, however, nowadays a situation like yours should not happen, because the directory will remain the same.

Sorry for inconvenience anyway. Please just manually delete the old folder.

[sunep]

It might be quite old but it happened,but I can imagine that it is quite normal to have old packs around, I normally just copy the pack folder over when I install a new vvvv version.

And since it is quite difficult to figure out which version you have installed and it is easy to miss an update, I would say my case is quite likely to happen. And it does the some fiddling around to find out why it is not working.

On Sun, Mar 19, 2017, 03:47 Marko Ritter notifications@github.com wrote:

Could it be that the old folder vvvv-Message_x64 comes from a quite old install (back from the days without vpm)? vpack files might have the power to do what you ask, however, nowadays a situation like yours should not happen, because the directory will remain the same.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/velcrome/vvvv-Message/issues/26#issuecomment-287590260, or mute the thread https://github.com/notifications/unsubscribe-auth/AFMcc1Sf94F3tXaPX4mVW_vwMdXMosthks5rnJdNgaJpZM4Mhi0E .

-- More about and by me: http://sunep.net/ https://www.facebook.com/MOTORSAW/

[velcrome]

@microdee

what would you do? is it a good idea to delete directories, that might have been created by previous versions, with a (slightly) different name?