Yes, use brewbuild for that regardless of platform (you have to download/extract the module first), or just perlbrew exec cpanm Module::Name if on *nix or berrybrew cpanm Module::Name if on Windows.
The Test::BrewBuild software is more geared to developers, to test their own modules. However, it isn't limited to just devs, if you actually fetch the source of a module (and if you want distributed testing, have access to the git repo that contains the module's source). Either way, perlbrew, berrybrew are spectacular resources to ensure a module will install properly on a system Perl, without affecting the system perl. The distributed nature of Test::BrewBuild was an early idea, pushed forward by a request.
| [reply]
[d/l]
[select] |
Right. When I was beginning in Perl, I would think nothing of getting a CPAN module and trying it out in my one and only Strawberry installation.
Now, I think first: Hey, what are the chances that this module will lead to a dead-end and clutter up my installation? So, yes, I do treat it like a "production" system now.
Or, as Orson Welles said in the Paul Masson commercials: "We will sell no wine before its time."
| [reply] |
When experimenting with CPAN modules, I sometimes create a git repository in my perl5/lib root. I can then easily switch between different versions and combinations of modules, and just throw away all the changes if I'm not satisfied with the results. (An example was described in my blog).
($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
| [reply]
[d/l] |
