… | |
… | |
81 | Maintaining your own custom perl build can be a pain in the ass, and while |
81 | Maintaining your own custom perl build can be a pain in the ass, and while |
82 | F<staticperl> tries to make this easy, it still requires a custom perl |
82 | F<staticperl> tries to make this easy, it still requires a custom perl |
83 | build and possibly fiddling with some modules. PAR is likely to produce |
83 | build and possibly fiddling with some modules. PAR is likely to produce |
84 | results faster. |
84 | results faster. |
85 | |
85 | |
|
|
86 | Ok, PAR never has worked for me out of the box, and for some people, |
|
|
87 | F<staticperl> does work out of the box, as they don't count "fiddling with |
|
|
88 | module use lists" against it, but nevertheless, F<staticperl> is certainly |
|
|
89 | a bit more difficult to use. |
|
|
90 | |
86 | =back |
91 | =back |
87 | |
92 | |
88 | =head1 HOW DOES IT WORK? |
93 | =head1 HOW DOES IT WORK? |
89 | |
94 | |
90 | Simple: F<staticperl> downloads, compile and installs a perl version of |
95 | Simple: F<staticperl> downloads, compile and installs a perl version of |