Why does the strawberry MSI installer allow to overwrite an existing installation? I'm too lazy to set up a test environment, but I would at least expect a big fat warning when doing so. If not, that's a bug in the installer (emphasis mine). If there is a warning, well, it is not big enough for at least two users. The release notes for the current release don't contain a warning. Also, no warnings on the homepage or the support page. And no open issue requesting a warning on the issues page.

I am in vehement agreement with Alexander, as you'd expect. I guess it's just a limitation in the MSI internals that it doesn't detect an existing installation of Strawberry where we are about to install, but somewhere in the web site for Strawberry there should be A WARNING IN CAPS., and I did look at the support page.

As an aside, I am using berrybrew to manage multiple StrawberryPerl installations now. It's a little weird (overnight my $PATH lost the element pointing to the Strawberry I was using {I swear}). Setting the $PATH requires Admin privileges and that a bit of an inconvenience. But I am repeating what I posted about in another node in this thread, sorry. Anyway, live and learn.

  Soren