summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTatsuhiko Miyagawa <miyagawa@bulknews.net>2013-08-07 11:58:57 -0700
committerTatsuhiko Miyagawa <miyagawa@bulknews.net>2013-08-07 11:58:57 -0700
commitd2b8bacff13dcb8224a95a5b140522d29e015594 (patch)
treefc199cb642a8a09ca2b7ec3ef4e0dd715147928d
parentc65fea9033a844f2452252a65db590124f327a4c (diff)
downloadcarton-d2b8bacff13dcb8224a95a5b140522d29e015594.tar.gz
Add notes on differernt Perl versions
-rw-r--r--lib/Carton.pm18
1 files changed, 18 insertions, 0 deletions
diff --git a/lib/Carton.pm b/lib/Carton.pm
index 7b274e5..65c8801 100644
--- a/lib/Carton.pm
+++ b/lib/Carton.pm
@@ -113,6 +113,24 @@ C<--deployment> option, you can avoid querying for a database like
CPAN Meta DB or downloading files from CPAN mirrors upon deployment
time.
+=head1 PERL VERSIONS
+
+When you take a snapshot in one perl version and deploy on another
+(different) version, you might have troubles with core modules.
+
+The simples solution, which might not work for everybody, is to use
+the same version of perl in the development and deployment.
+
+To enforce that, you're recommended to use L<plenv> and
+C<.perl-version> to lock perl versions in development.
+
+You can also specify the minimum perl required in C<cpanfile>:
+
+ requires 'perl', '5.16.3';
+
+and carton (and cpanm) will give you errors when deployed on hosts
+with perl lower than the specified version.
+
=head1 COMMUNITY
=over 4