What sent me down the road of forking berrybrew and modifying it was writing Test::BrewBuild... you can set up Unix Perlbrew and Windows berrybrew servers wherever you want, and using Test::BrewBuild and its utility components, send module builds to these remote servers, and they will all test your module against all of their installed versions of Perl, and return the results:

# within a module directory... 

bbdispatch -t localhost -t 192.168.252.90 -t 192.168.252.96 -t 192.168
+.252.95
 
192.168.252.95 - x86_64-linux
 
5.22.1 :: PASS
 
192.168.252.90 - MSWin32-x64-multi-thread
 
5.18.4 :: PASS
5.22.1 :: PASS
 
localhost - MSWin32-x64-multi-thread
 
5.22.1 :: PASS
 
192.168.252.96 - amd64-freebsd
 
5.22.1 :: PASS
5.23.7 :: PASS
5.8.9 :: FAIL
5.10.1 :: FAIL
5.18.4 :: FAIL
[download]

Yikes. It looks like your older Perl installations on your amd64-freebsd server are not quite ready for showtime.

Seriously, that is pretty neat how it just doesn't care whether it is a Unix or Windows server, it just does it.

...or, I was re-writing a module to be v5.6.0 compliant while I created the examples for this module, and wasn't quite there yet, or, FreeBSD has some issues with locking files, which is what I may have been debugging in the module I based these examples on ;)