Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Pinto is a sophisticated tool for managing Perl module dependencies. You may have heard about it from my presentation at YAPC earlier this year. In the last few months, Pinto has continued to evolve. The latest release includes a version control mechanism that allows you to review changes to your dependency stack and roll the stack back to a prior revision.

If your application has ever broken unexpectedly when a new version of a dependency is released to CPAN, or if you've struggled to create builds with consistent versions of your dependencies, then Pinto might be the tool you need. So I invite you to give it a try and send me your feedback. Some features are still experimental, so I recommend installing it into a sandbox. Here's how to get started:

# Install into the "sandbox" directory cpanm --local-lib=sandbox Pinto App::Pinto # Get a listing of available pinto commands perl -Isandbox/lib/perl5 sandbox/bin/pinto commands

Pinto has extensive documentation too. Pinto::Manual::QuickStart shows sample commands for common operations. Pinto::Manual::Tutorial is a step-by-step explanation of how to use Pinto. Lastly, Pinto::Manual::Introduction gives the big-picture of why Pinto exists in the first place.

I look forward to hearing what you all think.

-Jeff

In reply to Announcing: Pinto by jthalhammer

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others having an uproarious good time at the Monastery: (3)
As of 2024-04-24 18:39 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found