Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

cpanfile(3pm) [debian man page]

cpanfile(3pm)						User Contributed Perl Documentation					     cpanfile(3pm)

cpanfile - A format for describing CPAN dependencies for Perl applications SYNOPSIS
requires 'Catalyst', '5.8000'; requires 'CatalystX::Singleton', '>= 1.1000, < 2.000'; recommends 'JSON::XS', '2.0'; conflicts 'JSON', '< 1.0'; on 'test' => sub { requires 'Test::More', '>= 0.96, < 2.0'; recommends 'Test::TCP', '1.12'; }; on 'develop' => sub { recommends 'Devel::NYTProf'; }; VERSION
"cpanfile" describes CPAN dependencies required to execute associated Perl code. Place the "cpanfile" in the root of the directory containing the associated code. For instance, in a Catalyst application, place the "cpanfile" in the same directory as "myapp.conf". Tools supporting "cpanfile" format (e.g. cpanm and carton) will automatically detect the file and install dependencies for the code to run. AUTHOR
The format (DSL syntax) is inspired by Module::Install and Module::Build::Functions. "cpanfile" specification (this document) is based on Ruby's Gemfile <> specification. SEE ALSO
CPAN::Meta::Spec Module::Install Carton perl v5.14.2 2012-04-14 cpanfile(3pm)

Check Out this Related Man Page

CARTON(1p)						User Contributed Perl Documentation						CARTON(1p)

carton - Perl module dependency manager (aka Bundler for Perl) SYNOPSIS
# On your development environment > cat cpanfile requires 'Plack', 0.9980; requires 'Starman', 0.2000; > carton install > git add cpanfile carton.lock > git commit -m "add Plack and Starman" # Other developer's machine, or on a deployment box > carton install > carton exec -Ilib -- starman -p 8080 myapp.psgi WARNING
This software is under heavy development and considered ALPHA quality till its version hits v1.0.0. Things might be broken, not all features have been implemented, and APIs are likely to change. YOU HAVE BEEN WARNED. DESCRIPTION
carton is a command line tool to track the Perl module dependencies for your Perl application. The managed dependencies are tracked in a carton.lock file, which is meant to be version controlled, and the lock file allows other developers of your application will have the exact same versions of the modules. TUTORIAL
Initializing the environment carton will use the .carton directory for local configuration and the local directory to install modules into. You're recommended to exclude these directories from the version control system. > echo .carton/ >> .gitignore > echo local/ >> .gitignore > git add carton.lock > git commit -m "Start using carton" Tracking the dependencies You can manage the dependencies of your application via cpanfile. # cpanfile requires 'Plack', 0.9980; requires 'Starman', 0.2000; And then you can install these dependencies via: > carton install The modules are installed into your local directory, and the dependencies tree and version information are analyzed and saved into carton.lock in your directory. Make sure you add carton.lock to your version controlled repository and commit changes as you update dependencies. This will ensure that other developers on your app, as well as your deployment environment, use exactly the same versions of the modules you just installed. > git add cpanfile carton.lock > git commit -m "Added Plack and Starman" Deploying your application Once you've done installing all the dependencies, you can push your application directory to a remote machine (excluding local and .carton) and run the following command: > carton install This will look at the carton.lock and install the exact same versions of the dependencies into local, and now your application is ready to run. Bundling modules carton can bundle all the tarballs for your dependencies into a directory so that you can even install dependencies that are not available on CPAN, such as internal distribution aka DarkPAN. > carton bundle will bundle these tarballs into local/cache directory, and > carton install --cached will install modules using this local cache. This way you can avoid a dependency on CPAN meta DB and at a deploy time, or you can have dependencies onto private CPAN modules aka DarkPAN. COMMUNITY
<> Code repository, Wiki and Issue Tracker <irc://> IRC chat room AUTHOR
Tatsuhiko Miyagawa COPYRIGHT
Tatsuhiko Miyagawa 2011- LICENSE
This software is licensed under the same terms as Perl itself. SEE ALSO
cpanm Bundler <> pip <> npm <> perlrocks <> only perl v5.14.2 2012-05-12 CARTON(1p)
Man Page

Featured Tech Videos