O'Reilly Open Source Convention
Books Safari Bookshelf Conferences O'Reilly Network

Arrow Home
Arrow Registration
Arrow Speakers
Arrow Keynotes
Arrow Tutorials
Arrow Sessions
Arrow At-a-Glance
Arrow Wiki
Arrow BOFs
Arrow Events
Arrow Exhibitors
Arrow Sponsors
Arrow Hotel/Travel
Arrow Venue Map
Arrow See & Do
Arrow Tips for
Arrow Press
Arrow Mail List



Using CPAN Tools for In-House Development
Autrijus Tang, President, OurInternet, Inc. | The Elixir Initiative
Brian Ingerson, Free Agent, Social Text, Inc.

Track: Perl
Date: Thursday, July 29
Time: 10:45am - 11:30am
Location: Salon G


Dubbed as Perl's "killer application," the CPAN toolchain underwent a massive reengineering during the past few years, resulting in a set of loosely connected tools. Learn to leverage these utilities for internal development, to simplify code authoring, testing, feedback, packaging, deployment, and quality control.

Overview of CPAN

  • Technical architecture
  • Cultural mechanism
  • Loosely coupled services
  • How CPAN works for you

  • Efficiently locate resources
  • Different levels of reusing
  • Model internal development after CPAN
  • CPAN toolchain: Old and New

  • CPAN.pm, MakeMaker, h2xs and Test.pm
  • Design principles for new tools
  • How pieces work together

  • The default shell: "Digital Hub" for CPAN
  • Integration with native package managers
  • Case study: A local CPAN for your organization
  • Test::More

  • Swiss-army knife for Quality Assurance
  • Manual testing and automated testing
  • Case study: Smoke testing with Tinderbox
  • Module::Build

  • Pure-perl deployment engine
  • Customizations, sans Makefile magic
  • Case study: Client-side application deployment
  • Module::Install

  • Self-attached installer backend
  • Great for roll-your-own MakeMakers
  • Case study: Site-specific installation policy
  • Module::ScanDeps

  • Recursively scan for prerequisites
  • Automatically generate Build.PL configs
  • Case study: Application packaging with PAR.pm
  • ExtUtils::AutoInstall

  • Autoconf on steroids
  • Probing and installation for user-requested features
  • Case study: Writing interactive Makefile.PL/Build.PL
  • Module::Signature

  • CPAN checksums is now PGP-protected
  • Your modules can be signed, too
  • Case study: Automatic detection of trojan code
  • Test::Reporter

  • Interface for the CPAN Testers service
  • Integration with Request Tracker
  • Case study: Buliding a "Quality Feedback Wizard"
  • Module::CPANTS

  • Automated module testing
  • Reporting back all sorts of metadata
  • Measure Kwalitee quantatively

  • O'Reilly Home | Privacy Policy

    © 2004, O'Reilly Media, Inc.