/ 
Pinto-0.080
River stage one • 3 direct dependents • 5 total dependents
/ Pinto::Manual::Installing

NAME

Pinto::Manual::Installing - Tips for installing Pinto

VERSION

version 0.080

SYNOPSIS

For the impatient...

curl -L http://getpinto.stratopan.com | bash
source ~/opt/local/pinto/etc/bashrc

And then possibly...

echo source ~/opt/local/pinto/etc/bashrc >> ~/.bashrc

APPLICATION VERSUS LIBRARY

For most situations, Pinto is more like an application than a library. It is a tool that you use to develop and deploy your code, but Pinto itself is not part of your code. Pinto also has a lot of dependencies, some of which may conflict with or complicate your code.

INSTALLING AS AN APPLICATION

For the reasons above, I recommend installing Pinto as a stand-alone application in its own sandbox. That way, it doesn't pollute your environment with its dependencies. Nor will you pollute Pinto with changes to your environment, so Pinto will function even when your other environment dependencies are broken. And hopefully, you can use Pinto to help fix whatever broke!

Step 1: Run the pinto installer script

The installer script at getpinto.stratopan.com is just a wrapper around cpanm, which installs pinto in a self-contained directory:

# If you have curl...
curl -L http://getpinto.stratopan.com | bash

# If you use wget...
wget -O - http://getpinto.stratopan.com | bash

All the dependent modules will come from a curated repository on stratopan.com. These aren't always the latest versions of things, but they are versions that I know will work.

Step 2: Setup the pinto environment

The pinto installer generates a setup script for you. By default, it is located at ~/opt/local/pinto/etc/bashrc. To load that setup into your current shell, just give this command:

source ~/opt/local/pinto/etc/bashrc

To make these settings part of your everyday shell environment, just add that last command to your ~/.profile or ~/.bashrc or whatever setup file is appropriate for your shell.

If you wish to customize any of the other environment variables that pinto uses, you can place those commands in ~/.pintorc. If that file exists, the setup script will source them as well. See pinto for a list of the relevant environment variables.

INSTALLING AS A LIBRARY

If you're going to be hacking on Pinto itself, or want to try building on the API directly, then you can install Pinto straight into your development environment, just like you would do for any other module.

Just beware that Pinto has lots of dependencies. And if you subsequently upgrade any of those dependencies to something that breaks Pinto, then you might find yourself in a pickle. The whole point of Pinto is to help you manage your dependencies, so if you break Pinto, it won't be able to help you.

OTHER INSTALLATION OPTIONS

Naturally, installation procedures will vary from one environment to another. If this procedure doesn't work for you, or if you'd like to suggest a procedure for a different environment (e.g. Windows, Perlbrew, Strawberry Perl, etc.), then please contact me. Your contributions would be greatly appreciated.

SEE ALSO

Pinto::Manual::QuickStart

Pinto::Manual::Tutorial

Pinto (the library)

pinto (the command)

CONTRIBUTORS

  • Cory G Watson <gphat@onemogin.com>

  • Jakob Voss <jakob@nichtich.de>

  • Jeff <jeff@callahan.local>

  • Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>

  • Jeffrey Thalhammer <jeff@imaginative-software.com>

  • Karen Etheridge <ether@cpan.org>

  • Michael G. Schwern <schwern@pobox.com>

  • Steffen Schwigon <ss5@renormalist.net>

  • Wolfgang Kinkeldei <wolfgang@kinkeldei.de>

  • Yanick Champoux <yanick@babyl.dyndns.org>

AUTHOR

Jeffrey Ryan Thalhammer <jeff@stratopan.com>

COPYRIGHT AND LICENSE

This software is copyright (c) 2013 by Jeffrey Ryan Thalhammer.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.