CARTON-CHECK(1p) User Contributed Perl Documentation CARTON-CHECK(1p)NAME
carton-check - Check if your cpanfile and local environment are in sync
SYNOPSIS
carton check
DESCRIPTION
This command checks the consisntency between yoru cpanfile and the local environment.
MISSING MODULES
If one of the modules specified in your cpanfile are not found in your local environment, "carton check" will warn you about this:
$ carton check
Following dependencies are not satisfied. Run `carton install` to install them.
JSON (2.00)
You can run "carton install" again to reinstall these missing dependencies.
UNUSED MODULES
If one of the modules in the local environment (i.e. local library path) are not specified in your cpanfile, you'll get a warning like
this:
$ carton check
Following modules are found in local but couldn't be tracked from your cpanfile
CGI.pm-3.55
FCGI-0.73
This means you probably installed this module in an ad-hoc mode so you have to add it to cpanfile, or you originally declared the
dependencies but found out that you don't need it, so deleted from your cpanfile. In that case you can uninstall the module with the
uninstall command.
perl v5.14.2 2012-05-12 CARTON-CHECK(1p)
Check Out this Related Man Page
Carton::Doc::Install(3pm) User Contributed Perl Documentation Carton::Doc::Install(3pm)NAME
Carton::Doc::Install - Install the dependencies
SYNOPSIS
carton install [--deployment] [--path=PATH] [modules...]
DESCRIPTION
Install the dependencies for your application. This command has two modes and the behavior is slightly different.
DEVELOPMENT MODE
carton install (no arguments)
If you run "carton install" without any arguments and if cpanfile exists, carton will scan dependencies from cpanfile and install the
modules.
In either way, if you run "carton install" for the first time (i.e. carton.lock does not exist), carton will fetch all the modules
specified, resolve dependencies and install all required modules from CPAN.
If carton.lock file does exist, carton will still try to install modules specified or updated in cpanfile, but uses carton.lock for the
dependency resolution, and then cascades to CPAN.
carton will analyze all the dependencies and their version information, and it is saved into carton.lock file. It is important to add
carton.lock file into a version controlled repository and commit the changes as you update your dependencies.
DEPLOYMENT MODE
If you specify the "--deployment" command line option or the carton.lock exists and cpanfile does not exist, carton will fetch all remote
modules and use the dependencies specified in the carton.lock instead of resolving dependencies.
CONSERVATIVE UPDATE
"carton install" doesn't update the modules already installed into local library path as long as the version is satisfied.
For example, one day you install URI-1.50 from CPAN:
> carton install URI
Successfully installed URI-1.50
Few weeks later, URI module is updated to 1.51 on CPAN. If you run the "carton install URI" again:
> carton install URI
You have URI (1.50)
because you haven't specified the version number, carton won't update the module in your local library path.
WARNINGS: following commands are not implemented
If you want to update to the latest version of CPAN, you can either use "carton update" command, or specify the required version either in
your cpanfile.
> carton update URI
> cat cpanfile
requires 'URI', 1.51;
Any of those will upgrade URI to the latest one from CPAN, and the version specified in the carton.lock will be bumped.
OPTIONS --deployment
Force the deployment mode and carton will ignore cpanfile contents.
--path
Specify the path to install modules to. Defaults to local in the current directory.
perl v5.14.2 2012-04-12 Carton::Doc::Install(3pm)