search

chocolatey-community / chocolatey-test-environment

A testing setup related to how the Chocolatey Package Verifier runs testing. Used for manual testing or prior to submission
Apache License 2.0
117 stars 185 forks source link

Old VirtualBox version requirement #24

Open teknowledgist opened 6 years ago

teknowledgist commented 6 years ago

The "suggestion" for using VirtualBox 4.x (rather than 5.x) seems really outdated. Although there is a 4.3.40 package that was put out there just a couple weeks ago, the last previous 4.x release was almost 2 years ago with many 5.x releases since then.

I already have several VMs happily running in v5.2. I'd prefer to avoid the need to scrap those, uninstall VirtualBox, and install what seems reasonable to assume is a "less modern" version just so I can occasionally test a package that behaves for me on other VMs but fails automated testing. At the same time, I am stuck with packages that can't be approved because they fail.

While I am (just barely) astute enough to install and use VirtualBox, I am not well versed on it. I really don't know how the changes from 4 to 5 may have impacted things. What are the implications of using the Chocolatey-test-environment with v5, and what are the chances that the test environment can be updated to work with VirtualBox 5.x?

Thanks.

basictheprogram commented 6 years ago

I never saw the, "Virtualbox 4.3.28+ (5.x may have issues, so try to stay in 4.3.x series)" from chocolatey-test-environment :-( I've always used a 5.x Virtualbox on macOS and linux.

I have not run into any problems using Virtualbox 5.x. My fork of the chocolatey-test-environment uses WindowsServer2016 (from Stefan-Schere fork of packer-windows) works great.

Using all of the above I could pack draftsight and install it without any problems.

mgmax commented 8 months ago

Issue can be closed, the current README says "VirtualBox 5.2+".