I've released version 1.36 of berrybrew, the Perlbrew for Windows. I've also reached out to see how I can become part of the Strawberry Perl team to get back on track with the release of new Strawberry Perls.
If you have any information on the release procedure for Strawberry, or know anyone on that team I might be able to contact to get things moving forward again, please let me know.
This release contains one significant new feature, the ability to use Powershell as the shell when opening or using a Perl. In the UI, when you "Open" your current Perl, or "use" any Perl you have installed, if the "Use Powershell" option is checked, instead of a cmd.exe shell, you'll be presented with a Powershell one instead (same applies for the command line
berrybrew use $version.
The other changes in this release enhance the unit testing infrastructure, and the tests themselves.
Other notable changes since my last blog post:
berrybrew associate command now has an alias of
assoc for fewer keystrokes
- Better exception handling in several cases
- Documentation clarifications
- Removed the
upgrade command. It's now recommended to use the Installer to manage upgrades
- Fix issue when using berrybrew to manage file associations where arguments passed to perl were being handled incorrectly
- Unit test infrastructure enhancements
I've released version 1.34 of berrybrew.
- UI elements now update on the fly, so all changes are reflected immediately
- You can 'use' any version of installed Perl from the UI, which opens up a new CLI window set to use the selected version
- You can now fetch the updated list of Strawberry Perls available through the UI
- Cloning installed Perls as well as a myriad of other operations can now be done through the UI
- The API has been updated so that internal objects are updated live-time. This makes having long-running processes possible
- Build/Test infrastructure updates
- Documentation updates
- Minor bug fixes
I've just got a new full time job, programming in Perl... finally, after several years of looking for that perfect work environment. Some of it will be on Windows (which I haven't used except for developing
berrybrew), so I'm actually looking forward to using my own software, especially how useful its become thanks to the new UI I've developed.
I've released berrybrew version 1.33. This version has significant enhancements, along with some bug fixes and handling of some uncaught exceptions. The changes reflect versions 1.30 to 1.33.
Major changes include:
- Allows you to install, switch to, remove and use Strawberry Perls directly
- Can now spawn a CLI window for any Perl you have installed
- Allows you to spawn a CLI window for the currently active Perl
- Provides access to modify several of the core configuration options (debug, file association etc)
- Allows you to disable all berrybrew Perls and restore to system default
- Performs an upgrade on any previous berrybrew install
- Adds any new configuration options, while preserving the values of any previously set existing ones
- Provides facility to install the most recent version of Strawberry Perl
- Allows you to have berrybrew manage the .pl file association
- Allows you to have the UI run at system startup
- Aborts if trying to install the same version that's already installed
- You can now leave off the 32/64 bit prefix on a Perl name, and we'll default to _64
- All execution paths return a proper exit code
- Added new berrybrew hidden command, lists all, well, hidden commands
For all other changes, please refer to the Changes file.
Merry Christmas fellow Perlers!
I have been working tirelessly on the newest version of berrybrew, and thought there's no better day to release it.
It brings significant new features:
- Added a UI, runs out of the System Tray, allows installing, removing and switching Perls using a button
- Added new
associate command, allowing
berrybrew to manage
.pl file associations
berrybrew-refresh command, to be run after switching perls. No more having to re-open command line windows
- If a newer point release of a major version is introduced, we now seamlessly integrate installed previous point-releases into the Perls available
- Configuration options are now based in the Windows Registry
- Added new
options command, allows changing configuration options at runtime
- We now supply a
bb command, which is simply a short-hand form for
- Greatly enhanced the self-extracting installer
- Much more precise handling of the
PATH environment variable
- More graceful handling of exceptions
info command which displays various internal directory path information
- Added new hidden/developer commands
The UI is automatically installed by the installer. It starts and resides hidden in the System Tray until it is needed. Simply click the
berrybrewUI icon to bring up a Windows Form window. You can install, remove and switch between Perl instances.
When switching Perls using the UI, if you have open CLI windows, you still need to run
berrybrew-refresh or open a new CLI window to refresh the path information.
To exit the
berrybrewUI, right-click on the System Tray icon, and click
There are several enhancements to the installer:
We properly check for existing installations, and ask confirmation questions on the actions, depending on information about the previous install. In some cases, we'll ask to do a direct upgrade, in others, we'll ask if we can simply disable the old version before installing the new. See caveats below.
We now ask for the directory location of the Perl instance directory (internally referred to as
root_dir). If you specify a location that a previous
berrybrew used, we'll merrily inherit all of the previously installed Perls.
Uninstall is available through Add/Remove programs
UI provides select-able options to 1) install the most recent version of Perl, 2) start the UI at system startup, 3) allow
berrybrew to manage
.pl file association
Caveats: If you have a previous version of
berrybrew where you've changed any of the default configuration variables in the
config.json file, you will have to manually update these options after install of the new version. Simply run
berrybrew options on the new version to see what values are set. Then, open up your previous berrybrew's
config.json file, and for each difference, simply run
berrybrew options directive value where
directive is the name of the option, and
value is the value from the old config file. This will be automated in a future release.
You can now allow
berrybrew to manage the
.pl file association. We implement this in a similar way to Unix, in which when we're managing this association, the system will use the first
perl found in the
PATH environment variable.
- Check current file association with
- Allow us to manage the association:
berrybrew associate set
- Revert back to the previous association:
berrybrew associate unset
- Broke out the dev build script into three:
build_ui.bat. Left in place the
build.bat script, which performs all three actions
- The dev and test builds automatically create and use their own respective registry locations (
I've spent more than four years working on Raspberry Pi stuff for Perl, and although it's only garnered a relatively small but thorough interest, it's been a wonderful one to be a part of.
Mozilla has opened up a new IoT Platform, and I'm wondering if it'd be worth the time to provide a Perl interface to it or not.