This is an automated email from the git hooks/post-receive script. kanashiro-guest pushed a commit to branch master in repository carton.
commit efa9826757a7a3d03096933b1e2525fae365ceb6 Author: Tatsuhiko Miyagawa <miyag...@bulknews.net> Date: Wed Oct 19 12:27:14 2011 +0900 Document perlbrew lib and carton --- lib/Carton/Doc/FAQ.pod | 44 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) diff --git a/lib/Carton/Doc/FAQ.pod b/lib/Carton/Doc/FAQ.pod index 7349762..9d93d71 100644 --- a/lib/Carton/Doc/FAQ.pod +++ b/lib/Carton/Doc/FAQ.pod @@ -79,4 +79,48 @@ your application. The I<carton.lock> file can always be generated out of the local library path, and carton can reproduce the tree using the lock file on other machines. +=head2 I'm already using perlbrew and local::lib. Can I use carton with this? + +If you're using L<local::lib> already with L<perlbrew> perl, possibly +with the new C<perlbrew lib> command, that's great! There are multiple +benefits over using L<perlbrew> and L<local::lib> for development and +use L<Carton> for deployment. + +The best practice and workflow to get your perl environment as clean +as possible with lots of modules installed for quick development would +be this: + +=over + +=item * + +Install fresh perl using perlbrew. The version should be the same +against the version you'll run on the production environment (if any). + +=item * + +Once the installation is done, use C<perlbrew lib> command to create a +new local lib environment (let's call it I<devel>) and always use the +library as a default environment. Install as many modules as you would +like into the I<devel> library path. + +This ensures to have a vanilla C<perl> library path as clean as +possible. + +=item * + +When you build a new project that you want to manage dependencies via +Carton, turn off the I<devel> local::lib and create a new one, like +I<carton>. Install L<Carton> and all of its dependencies to the +I<carton> local::lib path. Then run C<carton install> like you +normally do. + +Becuase I<devel> and I<carton> are isolated, the modules you installed +into I<devel> doesn't affect the process when carton builds the +dependency tree for your new project at all. This could often be +critical when you have a conditional dependency in your tree, like +L<Any::Moose>. + +=back + -- Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/carton.git _______________________________________________ Pkg-perl-cvs-commits mailing list Pkgemail@example.com http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-cvs-commits