I recently had one of my clients ask me if I could automate installing berrybrew along with specific existing and new Perl instances.
I've taken a couple of days to get things to the point where my release automation is doing the right thing. I've tested it on a half dozen Windows 10 VMs, and things appear to work correctly. That said, I probably have differing configurations on my Windows machines than others do, so I'm hoping I can get some volunteers to test it out and see if there are any oddities.
The installer will install the 1.27 version, and is located right here.
Defaults that should be visible throughout the process:
- License should be displayed
- Install directory should be "C:\Program Files (x86)\berrybrew"
- "Install Perl 5.30.0_64" should be displayed as a component, and checked
- You should see a couple of cmd windows open and close, then, if you've left the Perl install checkbox checked, a third cmd window will remain open displaying install progress. It should close upon completion
After the install is complete:
- echo %path% in a newly-opened cmd window should list "C:\Program Files (x86)\berrybrew\bin", and if you opted to install Perl 5.30.0 during install, you should see three paths all which should reflect "C:\berrybrew\5.30.0_64"
- perl -V should be 5.30.0
Uninstall: The uninstall program is inside of the install directory (by default, "C:\Program Files (x86)\berrybrew". After it's run, you should see (in yet another new cmd window:
- Both the berrybrew path should be gone, as should all three of the Perl paths that were created
- The "C:\Program Files (x86)\berrybrew" directory should remain, but be empty (I'm working on the removal of that dir)
- The "C:\berrybrew" directory should still exist, and so should the 5.30.0_64 directory within it
Re-installing after an uninstall will know if you've still got 5.30.0 installed and will bypass that part, but will "switch" to it before exiting.
I'm also wondering if any UAC/security warnings or boxes pop-up during install.
Thanks all!
-stevieb