Commented Feature: Package folder names with version numbers break version control and CI Build [1522]

When installing or updating a NuGet package, the package is placed in a folder that contains the version number of the package being installed.

This breaks version control, since the old package is not removed from version control and the new package is not added to it. In Subversion for example, this then requires a not insignificant amount of cleanup.

This problem also affects continuous integration build servers, where the build script usually needs to be edited to take account of the new path (I've run into this problem specifically with Machine.Specifications, which has a test runner that needs to be launched on the build server).

It would be really, really, REALLY useful if one could install a package into a folder that doesn't contain any version number, so that the folder name never,changes. This could be specified per-package in the user interface when the package is first installed, and/or as a default in the NuGet settings.
Comments: PS. I am ~not~ a powershell developer by far. Feel free to improve my code. This is actually my first powershell script that I have ever authored.