If you have version 1.13+, you can copy it in, and use berrybrew register to register it. If you don't have that version, copy the directory, then edit the data/perls_custom.json file in the berrybrew installation directory, and make it look something like (where ver: is the actual version number as downloaded):

[
  {
    "name": "whatever_you_want",
    "url": "",
    "file": "",
    "csum": "",
    "ver": "5.22.3"
  }
]
[download]

If you have existing custom perls, then that needs to be appended to the others. This new version will then be considered a legit "custom" version.

Thank you very much! Do not have berrybrew yet, so will surely have a newest version of it :-) so register should work. Have a lot of CPAN modules installed in my working version (just Strawberry Perl, no hacks - this is what you mean by custom perl, right?), do not want to repeat the installation if it can be avoided.

Yep, that's exactly what I mean :)

As of 1530 hrs MST on 20170801, the site is now back up, so forget the below:

First thing to note here is as of the last two days, Strawberry Perl's website is down, and berrybrew won't allow you to install any new instances at all until its back up. To use berrybrew in this case, you must put any instances in place and "register" them manually.

Under berrybrew, if you have an instance set up to how you like it, you can "clone" it as a template, or another duplicate full instance and have backups around.

See the clone documentation in the main binary documentation. Might want to have a look at the register part as well.

In doing a clone, if you have tmpl or template in the cloned name, they are treated special, and berrybrew will ignore them on all operations (ie. exec won't attempt to run anything against them.