# packages

pkgId: 46fccab8871dcae0770e15a2b49760ebe836f8cac50d592fc120f1ff120d3f30
name: asciidoc
arch: noarch
version: 8.2.6
epoch: 0
release: 1.rf
summary: Tool to convert AsciiDoc text files to DocBook, HTML or Unix man pages
url: http://www.methods.co.nz/asciidoc/
rpm_license: GPL
rpm_vendor: Dag Apt Repository, http://dag.wieers.com/apt/
rpm_group: Applications/Text
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: asciidoc-8.2.6-1.rf.src.rpm
rpm_packager: Dag Wieers <dag@wieers.com>
location_href: asciidoc-8.2.6-1.rf.noarch.rpm
checksum_type: sha256
description:
  AsciiDoc is a text document format for writing short documents, articles,
  books and UNIX man pages. AsciiDoc files can be translated to HTML and
  DocBook markups using the asciidoc(1) command.


pkgId: c228f0596969182e536d0e28d96768a5f87b9862dfbd26382e38c1c133a354c2
name: cron-harness
arch: noarch
version: 20060102
epoch: 0
release: 1
summary: Capture program output and email it only if nonzero exit status
url: http://www.endpoint.com/
rpm_license: GPL
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/File
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: cron-harness-20060102-1.src.rpm
rpm_packager: Jon Jensen <jon@endpoint.com>
location_href: cron-harness-20060102-1.noarch.rpm
checksum_type: sha256
description:
  cron-harness wraps other programs. If the progrma it runs returns an error
  exit value, it will either email its output somewhere (if the -e option is
  given) or simply send it to stdout (the default); otherwise it is silent.


pkgId: 7cb09acfa44c7af2be7df57a52debad8c16c940d73fbd38bc627d85a90b7ebd4
name: endpoint-repo
arch: x86_64
version: 1.6
epoch: 0
release: 1
summary: Yum configuration for End Point main RPM repository
url: https://packages.endpoint.com/
rpm_license: GPL
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: System Environment/Base
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: endpoint-repo-1.6-1.src.rpm
rpm_packager: Jon Jensen <jon@endpoint.com>
location_href: endpoint-repo-1.6-1.x86_64.rpm
checksum_type: sha256
description:
  This package contains the Yum configuration and public GnuPG signing keys
  for the End Point main RPM repositories.


pkgId: d8b09bd1ece6946508c9e7ff97efba724cd03d87fc33acda0976a559c22a4e1a
name: fping
arch: x86_64
version: 2.4b2
epoch: 0
release: 8.ep
summary: Scriptable, parallelized ping-like utility
url: http://www.fping.com/
rpm_license: BSD with advertising
rpm_vendor: End Point Corporation
rpm_group: Applications/Internet
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: fping-2.4b2-8.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: fping-2.4b2-8.ep.x86_64.rpm
checksum_type: sha256
description:
  fping is a ping-like program which can determine the accessibility of
  multiple hosts using ICMP echo requests. fping is designed for parallelized
  monitoring of large numbers of systems, and is developed with ease of
  use in scripting in mind.


pkgId: 6428586ed70def394c56ffccc8fe18b45acf5a6fe56f575ebdbad611cdef43bb
name: git
arch: x86_64
version: 1.8.4
epoch: 0
release: 1.ep
summary: Fast Version Control System
url: http://git-scm.com/
rpm_license: GPLv2
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Tools
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: git-1.8.4-1.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: git-1.8.4-1.ep.x86_64.rpm
checksum_type: sha256
description:
  Git is a fast, scalable, distributed revision control system with an
  unusually rich command set that provides both high-level operations
  and full access to internals.

  The git rpm installs the core tools with minimal dependencies.  To
  install all git packages, including tools for integrating with other
  SCMs, install the git-all meta-package.


pkgId: 88c7d4085e17db0ec7601a9c242353caa66acfa2b67f6e036395800ada3dd821
name: git-all
arch: noarch
version: 1.8.4
epoch: 0
release: 1.ep
summary: Meta-package to pull in all git tools
url: http://git-scm.com/
rpm_license: GPLv2
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Tools
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: git-1.8.4-1.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: git-all-1.8.4-1.ep.noarch.rpm
checksum_type: sha256
description:
  Git is a fast, scalable, distributed revision control system with an
  unusually rich command set that provides both high-level operations
  and full access to internals.

  This is a dummy package which brings in all subpackages.


pkgId: 1a0507afb85bc5d7cf761753c4654c0ecfe8d2c9fe6a08592d223ee5772de760
name: git-user
arch: noarch
version: 20111024
epoch: 0
release: 1
summary: Easily change author and committer for git commands
url: http://www.endpoint.com/
rpm_license: Public domain
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/File
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: git-user-20111024-1.src.rpm
rpm_packager: Jon Jensen <jon@endpoint.com>
location_href: git-user-20111024-1.noarch.rpm
checksum_type: sha256
description:
  git-user is a convenience wrapper for git commands that sets the author
  and committer from a predetermined list of usernames.


pkgId: f4b3c44382335898b710e47889979bae84a63df0be273fa0a772d3b93bd8bf78
name: local-perl
arch: x86_64
version: 5.14.1
epoch: 4
release: 162.ep
summary: Practical Extraction and Report Language, a local, non-threaded build
url: http://www.perl.org/
rpm_license: (GPL+ or Artistic) and (GPLv2+ or Artistic) and Copyright Only and MIT and Public Domain and UCD
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Languages
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-5.14.1-162.ep.x86_64.rpm
checksum_type: sha256
description:
  Perl is a high-level programming language with roots in C, sed, awk and shell
  scripting.  Perl is good at handling processes and files, and is especially
  good at handling text.  Perl's hallmarks are practicality and efficiency.
  While it is used to do a lot of different things, Perl's most common
  applications are system administration utilities and web programming.  A large
  proportion of the CGI scripts on the web are written in Perl.  You need the
  perl package installed on your system so that your system can handle Perl
  scripts.

  Install this package if you want to program in Perl or enable your system to
  handle Perl scripts.


pkgId: c42738d5fbf0ab17f523e7b27d3dfcf50dbf861f80d1817392d446d2f7aa0b6f
name: local-perl-Algorithm-Diff
arch: noarch
version: 1.1903
epoch: 0
release: 1
summary: Algorithm-Diff - Compute `intelligent' differences between two files / lists
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: This version released <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Algorithm-Diff-1.1903-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Algorithm-Diff-1.1903-1.noarch.rpm
checksum_type: sha256
description:
  require Algorithm::Diff;

      

      my $diff = Algorithm::Diff->new( \@seq1, \@seq2 );

      $diff->Base( 1 );   # Return line numbers, not indices
      while(  $diff->Next()  ) {
          next   if  $diff->Same();
          my $sep = '';
          if(  ! $diff->Items(2)  ) {
              printf "%d,%dd%d\n",
                  $diff->Get(qw( Min1 Max1 Max2 ));
          } elsif(  ! $diff->Items(1)  ) {
              printf "%da%d,%d\n",
                  $diff->Get(qw( Max1 Min2 Max2 ));
          } else {
              $sep = "---\n";
              printf "%d,%dc%d,%d\n",
                  $diff->Get(qw( Min1 Max1 Min2 Max2 ));
          }
          print "< $_"   for  $diff->Items(1);
          print $sep;
          print "> $_"   for  $diff->Items(2);
      }


      

      use Algorithm::Diff qw(
          LCS LCS_length LCSidx
          diff sdiff compact_diff
          traverse_sequences traverse_balanced );

      @lcs    = LCS( \@seq1, \@seq2 );
      $lcsref = LCS( \@seq1, \@seq2 );
      $count  = LCS_length( \@seq1, \@seq2 );

      ( $seq1idxref, $seq2idxref ) = LCSidx( \@seq1, \@seq2 );


      

      @diffs  = diff( \@seq1, \@seq2 );

      @sdiffs = sdiff( \@seq1, \@seq2 );

      @cdiffs = compact_diff( \@seq1, \@seq2 );

      traverse_sequences(
          \@seq1,
          \@seq2,
          {   MATCH     => \&callback1,
              DISCARD_A => \&callback2,
              DISCARD_B => \&callback3,
          },
          \&key_generator,
          @extra_args,
      );

      traverse_balanced(
          \@seq1,
          \@seq2,
          {   MATCH     => \&callback1,
              DISCARD_A => \&callback2,
              DISCARD_B => \&callback3,
              CHANGE    => \&callback4,
          },
          \&key_generator,
          @extra_args,
      );


pkgId: d817bf9caa3ccca79f8b86e7b98628a1b9301ae53880309f551b967e2ee03622
name: local-perl-Any-Moose
arch: noarch
version: 0.18
epoch: 0
release: 1
summary: Any-Moose - use Moose or Mouse modules
description: None.
url: http://www.cpan.org
rpm_license: Artistic
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Any-Moose-0.18-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Any-Moose-0.18-1.noarch.rpm
checksum_type: sha256
rpm_vendor:
  Shawn M Moore <sartak@gmail.com>, Florian Ragwitz <rafl@debian.org>, Stevan Little <stevan@iinteractive.com>, Tokuhiro Matsuno <tokuhirom@gmail.com>, Goro Fuji <gfuji@cpan.org>, Ricardo Signes <rjbs@cpan.org>


pkgId: 2e171431e37ea85ca75d0ec73d570664b710ae5ae53c0af87b27031d83520134
name: local-perl-AppConfig
arch: noarch
version: 1.66
epoch: 0
release: 1
description: None.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Wardley <abw@wardley.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-AppConfig-1.66-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-AppConfig-1.66-1.noarch.rpm
checksum_type: sha256
summary:
  AppConfig - AppConfig is a bundle of Perl5 modules for reading configuration files and parsing command line arguments.


pkgId: c2b7876d332ad79f8ed908ec9189dfc5352f19995d41075af15a62d142bdbea3
name: local-perl-Archive-Tar
arch: noarch
version: 1.76
epoch: 0
release: 162.ep
summary: A module for Perl manipulation of .tar files
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Archive-Tar-1.76-162.ep.noarch.rpm
checksum_type: sha256
description:
  Archive::Tar provides an object oriented mechanism for handling tar files.  It
  provides class methods for quick and easy files handling while also allowing
  for the creation of tar file objects for custom manipulation.  If you have the
  IO::Zlib module installed, Archive::Tar will also support compressed or
  gzipped tar files.


pkgId: 1d4139af6da10e3c816deecb045d2709977a9c4aa6f7d655ee75ab6d7979a530
name: local-perl-Archive-Zip
arch: noarch
version: 1.31_02
epoch: 0
release: 1
summary: Archive-Zip - Provide an interface to ZIP archive files.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ned Konz <perl@bike-nomad.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Archive-Zip-1.31_02-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Archive-Zip-1.31_02-1.noarch.rpm
checksum_type: sha256
description:
  The Archive::Zip module allows a Perl program to create, manipulate, read,
  and write Zip archive files.

  Zip archives can be created, or you can read from existing zip files.

  Once created, they can be written to files, streams, or strings. Members
  can be added, removed, extracted, replaced, rearranged, and enumerated.
  They can also be renamed or have their dates, comments, or other attributes
  queried or modified. Their data can be compressed or uncompressed as needed.

  Members can be created from members in existing Zip files, or from existing
  directories, files, or strings.

  This module uses the L<Compress::Raw::Zlib> library to read and write the
  compressed streams inside the files.

  One can use L<Archive::Zip::MemberRead> to read the zip file archive members
  as if they were files.


pkgId: 7030135f4469dbbee2a1cab74489bef64e193184d4b910849b03024a087247ed
name: local-perl-Authen-Captcha
arch: noarch
version: 1.023
epoch: 0
release: 1
summary: Authen-Captcha - Perl extension for creating captcha's to verify the human element in transactions.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Seth T. Jackson <sjackson@purifieddata.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Authen-Captcha-1.023-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Authen-Captcha-1.023-1.noarch.rpm
checksum_type: sha256
description:
  use Authen::Captcha;

    
    my $captcha = Authen::Captcha->new();

    
    $captcha->data_folder('/some/folder');

    
    $captcha->output_folder('/some/http/folder');

    
    

    my $captcha = Authen::Captcha->new(
      data_folder => '/some/folder',
      output_folder => '/some/http/folder',
      );

    
    my $md5sum = $captcha->generate_code($number_of_characters);

    
    
    
    my $results = $captcha->check_code($code,$md5sum);


pkgId: 6cd738e37d157f9a3ce416b2d2d93780e8cf10f6c69a010c56a78c210210fb0f
name: local-perl-Authen-Htpasswd
arch: noarch
version: 0.161
epoch: 0
release: 1
summary: Authen-Htpasswd - Interface to read and modify Apache .htpasswd files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: David Kamholz <dkamholz@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Authen-Htpasswd-0.161-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Authen-Htpasswd-0.161-1.noarch.rpm
checksum_type: sha256
description:
  This module provides a convenient, object-oriented interface to Apache-style
  F<.htpasswd> files.

  It supports passwords encrypted via MD5, SHA1, and crypt, as well as plain
  (cleartext) passwords.

  Additional fields after username and password, if present, are accessible via
  the C<extra_info> array.


pkgId: 730f18fda54f99a0d1cf11ef20b79cd80ebe8eb6bff20b0974ea1732a22e6bdf
name: local-perl-Barcode-Code128
arch: noarch
version: 2.01
epoch: 0
release: 1
summary: Barcode-Code128 - Generate CODE 128 bar codes
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: William R Ward <wrw@bayview.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Barcode-Code128-2.01-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Barcode-Code128-2.01-1.noarch.rpm
checksum_type: sha256
description:
  Barcode::Code128 generates bar codes using the CODE 128 symbology.  It
  can generate images in PNG or GIF format using the GD package, or it
  can generate a text string representing the barcode that you can
  render using some other technology if desired.

  The intended use of this module is to create a web page with a bar
  code on it, which can then be printed out and faxed or mailed to
  someone who will scan the bar code.  The application which spurred its
  creation was an expense report tool, where the employee submitting the
  report would print out the web page and staple the receipts to it, and
  the Accounts Payable clerk would scan the bar code to indicate that
  the receipts were received.

  The default settings for this module produce a large image that can
  safely be FAXed several times and still scanned easily.  If this
  requirement is not important you can generate smaller image using
  optional parameters, described below.

  If you wish to generate images with this module you must also have the
  GD.pm module (written by Lincoln Stein, and available from CPAN)
  installed.  Version 1.20 or higher of GD generates a PNG file, due to
  issues with the GIF patent.  If you want to create a GIF, you must use
  version 1.19 or earlier of GD.  However, most browsers have no trouble
  with PNG files.

  If the GD module is not present, you can still use the module, but you
  will not be able to use its functions for generating images.  You can
  use the barcode() method to get a string of "#" and " " (hash and
  space) characters, and use your own image-generating routine with that
  as input.

  To use the the GD module, you will need to install it along with this
  module.  You can obtain it from the CPAN (Comprehensive Perl Archive
  Network) repository of your choice under the directory
  C<authors/id/LDS>.  Visit http://www.cpan.org/ for more information
  about CPAN.  The GD home page is:
  http://stein.cshl.org/WWW/software/GD/GD.html


pkgId: d728c7d698c312357d11064d38b4a579a82967f56c020d10ba9ea121422045a8
name: local-perl-Bundle-InterchangeKitchenSink
arch: noarch
version: 1.06
epoch: 0
release: 2
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: End Point Corporation
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Bundle-InterchangeKitchenSink-1.06-2.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Bundle-InterchangeKitchenSink-1.06-2.noarch.rpm
checksum_type: sha256
summary:
  Bundle-InterchangeKitchenSink - A bundle of most all the modules nice to have for Interchange. A lot of stuff.

description:
  This bundle installs the prerequisites for Interchange 5.6.0 as well as some
  modules that are not strictly necessary.


pkgId: 0165d79b7065721911b1cb733470a528f4d8740e47d4a431262a91509f15ebf0
name: local-perl-Bundle-LWP
arch: noarch
version: 5.810
epoch: 0
release: 2
summary: Bundle-LWP - install all libwww-perl related modules
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: cpan
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Bundle-LWP-5.810-2.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Bundle-LWP-5.810-2.noarch.rpm
checksum_type: sha256
description:
  Bundle::LWP - installs all libwww-perl related modules

  Digest::MD5 - Needed to do Digest authentication
  HTML::HeadParser - To get the correct $res->base
  HTML::Parser - Need by HTML::HeadParser
  HTML::Tagset - Needed by HTML::Parser
  LWP - The reason why you need the modules above
  MIME::Base64 - Used in authentication headers
  Net::FTP 2.58 - If you want ftp://-support
  URI 1.10 - There are URIs everywhere


pkgId: 5b634451270b935d39dfe36cf6243b152e6fa06af8c84c715e1a5608d1962460
name: local-perl-Business-CreditCard
arch: noarch
version: 0.31
epoch: 0
release: 1
summary: Business-CreditCard - Validate/generate credit card checksums/names
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: MIT Media Lab <orwant@tpj.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Business-CreditCard-0.31-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Business-CreditCard-0.31-1.noarch.rpm
checksum_type: sha256
description:
  These subroutines tell you whether a credit card number is
  self-consistent -- whether the last digit of the number is a valid
  checksum for the preceding digits.

  The validate() subroutine returns 1 if the card number provided passes
  the checksum test, and 0 otherwise.

  The cardtype() subroutine returns a string containing the type of
  card.  The list of possible return values is more comprehensive than it used
  to be, but additions are still most welcome.

  Possible return values are:

    VISA card
    MasterCard
    Discover card
    American Express card
    enRoute
    JCB
    BankCard
    Switch
    Solo
    China Union Pay
    Laser
    Unknown

  "Not a credit card" is returned on obviously invalid data values.

  Versions before 0.31 may also have returned "Diner's Club/Carte Blanche" (these
  cards are now recognized as "Discover card").

  As of 0.30, cardtype() will accept a partial card masked with "x", "X', ".",
  "*" or "_".  Only the first 2-6 digits and the length are significant;
  whitespace and dashes are removed.  To recognize just Visa, MasterCard and
  Amex, you only need the first two digits; to recognize almost all cards
  except some Switch cards, you need the first four digits, and to recognize
  all cards including the remaining Switch cards, you need the first six
  digits.

  The generate_last_digit() subroutine computes and returns the last
  digit of the card given the preceding digits.  With a 16-digit card,
  you provide the first 15 digits; the subroutine returns the sixteenth.

  This module does I<not> tell you whether the number is on an actual
  card, only whether it might conceivably be on a real card.  To verify
  whether a card is real, or whether it's been stolen, or to actually process
  charges, you need a Merchant account.  See L<Business::OnlinePayment>.

  These subroutines will also work if you provide the arguments
  as numbers instead of strings, e.g. C<validate(5276440065421319)>.


pkgId: 04c155c5c0b7fac524767b4e3d12202c11e15af5d65c19c48c5b9d780ea9a3bb
name: local-perl-Business-CreditCard-Object
arch: noarch
version: 1.00
epoch: 0
release: 1
summary: Business-CreditCard-Object - a Credit Card object
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tony Bowden <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Business-CreditCard-Object-1.00-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Business-CreditCard-Object-1.00-1.noarch.rpm
checksum_type: sha256
description:
  This provides an OO interface around the Business::CreditCard module.
  You instantiate it with a card number, and can ask if it is valid, for
  a standardised version of the card number, and what type of card it is.


pkgId: 1d88451b32c5c4a9ae52390561c6cfcf8a0b3d6a8b7eeabe512ab2a8a857ca1f
name: local-perl-Business-Hours
arch: noarch
version: 0.10
epoch: 0
release: 1
summary: Business-Hours - Calculate business hours in a time period
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jesse Vincent (jesse@cpan.org)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Business-Hours-0.10-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Business-Hours-0.10-1.noarch.rpm
checksum_type: sha256
description:
  This module is a simple tool for calculating business hours in a time period.
  Over time, additional functionality will be added to make it easy to
  calculate the number of business hours between arbitrary dates.


pkgId: 342b437b26c4430938a1b0df5e77150d1ffd15607653dc3d763e4c1ecb6db5d6
name: local-perl-Business-OnlinePayment
arch: noarch
version: 3.02
epoch: 0
release: 1
summary: Business-OnlinePayment - Perl extension for online payment processing
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ivan Kohler <ivan-business-onlinepayment@420.am>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Business-OnlinePayment-3.02-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Business-OnlinePayment-3.02-1.noarch.rpm
checksum_type: sha256
description:
  Business::OnlinePayment is a generic module for processing payments
  through online credit card processors, electronic cash systems, etc.


pkgId: 82e6eb6ee535bd253cee82893af2fafac047de59113280fe672c30e3baed83e3
name: local-perl-Business-UPS
arch: noarch
version: 2.01
epoch: 0
release: 1
summary: Business-UPS - A UPS Interface Module
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Justin Wheeler <upsmodule@datademons.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Business-UPS-2.01-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Business-UPS-2.01-1.noarch.rpm
checksum_type: sha256
description:
  A way of sending four arguments to a module to get shipping charges
  that can be used in, say, a CGI.


pkgId: f06c13c7d805cfc4502dad7abee1f2fc16f668957cd1ee33e44ae1185bd56fd7
name: local-perl-CGI
arch: noarch
version: 3.51
epoch: 0
release: 162.ep
summary: Handle Common Gateway Interface requests and responses
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-CGI-3.51-162.ep.noarch.rpm
checksum_type: sha256
description:
  CGI.pm is a stable, complete and mature solution for processing and preparing
  HTTP requests and responses. Major features including processing form
  submissions, file uploads, reading and writing cookies, query string generation
  and manipulation, and processing and preparing HTTP headers. Some HTML
  generation utilities are included as well.

  CGI.pm performs very well in in a vanilla CGI.pm environment and also comes
  with built-in support for mod_perl and mod_perl2 as well as FastCGI.


pkgId: a64772f8e79f32fc9045d7629a7aaec9bc3fcfaea270ca9ead27e6969253da2a
name: local-perl-CGI-Application-Plugin-AutoRunmode
arch: noarch
version: 0.18
epoch: 0
release: 1
summary: CGI-Application-Plugin-AutoRunmode - CGI::App plugin to automatically register runmodes
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Thilo Planz <thilo@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-CGI-Application-Plugin-AutoRunmode-0.18-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-CGI-Application-Plugin-AutoRunmode-0.18-1.noarch.rpm
checksum_type: sha256
description:
  This plugin for CGI::Application provides easy
  ways to setup run modes. You can just write
  the method that implement a run mode, you do
  not have to explicitly register it with CGI::App anymore.

  There are two approaches:

  =over 4

  =item Declare run modes with subroutine attributes.

  You can flag methods in
  your CGI::App subclass with the attribute "Runmode" or "StartRunmode" (these
  attributes are case-insensitive)

  =item Declare that every method in a class is a run mode.

  You can assign a
  delegate object, all whose methods will become runmodes

  You can also mix both approaches.

  Delegate runmodes receive two parameters: The first one is the CGI::App
  instance, followed by the delegate instance or class name. This can be useful
  if you have delegate objects that contain state.

  It is possible to chain multiple delegates by specifying an array reference
  containing the delegate instances or class names. This chain is
  checked from left to right and the runmode will be delegated to the first match.

  =back

  It both cases, the resulting runmodes will have the same
  name as the subroutine that implements them. They are activated
  by a cgiapp_prerun hook provided by this plugin (if
  you are using CGI::Application older than version 4, hooks
  are not available, and you can import a cgiapp_prerun method
  instead).


pkgId: 579cc7b8850ba98725adfb177ef125f192a417d68e20d9de522d494560601c5d
name: local-perl-CGI-Application-Plugin-Config-YAML
arch: noarch
version: 0.01
epoch: 0
release: 1
summary: CGI-Application-Plugin-Config-YAML - add Config::YAML support to CGI::Application
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Atsushi Kobayashi <Eltnekokak@cpan.orgEgt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-CGI-Application-Plugin-Config-YAML-0.01-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-CGI-Application-Plugin-Config-YAML-0.01-1.noarch.rpm
checksum_type: sha256
description:
  This plug-in add Config::YAML support to CGI::Application.
  The usage of this plug-in is almost the same as CGI::Application::Plugin::Config::Simple.
  This plug-in can be easily used instead of CGI::Application::Plugin::Config::Simple.
  This plug-in refers to CGI::Application::Plugin::Config::Simple.


pkgId: af6fe87b371e1e234a6640c88c6e1a599c2d27f1fd25137f42394f2870e23b75
name: local-perl-CGI-Compile
arch: noarch
version: 0.15
epoch: 0
release: 1
summary: CGI-Compile - Compile .cgi scripts to a code reference like ModPerl::Registry
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tatsuhiko Miyagawa <miyagawa@bulknews.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-CGI-Compile-0.15-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-CGI-Compile-0.15-1.noarch.rpm
checksum_type: sha256
description:
  CGI::Compile is an utility to compile CGI scripts into a code
  reference that can run many times on its own namespace, as long as the
  script is ready to run on a persistent environment.

  B<NOTE:> for best results, load L<CGI::Compile> before any modules used by your
  CGIs.


pkgId: b007beab7e27c9b69cb8d4dc19c419dea05450928e05297c374e41a56c2e4977
name: local-perl-CGI-Emulate-PSGI
arch: noarch
version: 0.14
epoch: 0
release: 1
summary: CGI-Emulate-PSGI - PSGI adapter for CGI
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tokuhiro Matsuno <tokuhirom@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-CGI-Emulate-PSGI-0.14-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-CGI-Emulate-PSGI-0.14-1.noarch.rpm
checksum_type: sha256
description:
  This module allows an application designed for the CGI environment to
  run in a PSGI environment, and thus on any of the backends that PSGI
  supports.

  It works by translating the environment provided by the PSGI
  specification to one expected by the CGI specification. Likewise, it
  captures output as it would be prepared for the CGI standard, and
  translates it to the format expected for the PSGI standard using
  L<CGI::Parse::PSGI> module.


pkgId: 4ceadd5dd9e43487e47b59cf6e07891c086c7f3a5a7e15bf739f710e66fad443
name: local-perl-CPANPLUS
arch: noarch
version: 0.9103
epoch: 0
release: 162.ep
summary: API & CLI access to the CPAN mirrors
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-CPANPLUS-0.9103-162.ep.noarch.rpm
checksum_type: sha256
description:
  The CPANPLUS library is an API to the CPAN mirrors and a collection of
  interactive shells, commandline programs, etc, that use this API.


pkgId: c8f327c6e0896b17c9dbbc2c29894e680b9f14df4a51507db63c08b6204c2516
name: local-perl-Cache-Memcached
arch: noarch
version: 1.29
epoch: 0
release: 1
summary: Cache-Memcached - client library for memcached (memory cache daemon)
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Brad Fitzpatrick <brad@danga.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Cache-Memcached-1.29-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Cache-Memcached-1.29-1.noarch.rpm
checksum_type: sha256
description:
  This is the Perl API for memcached, a distributed memory cache daemon.
  More information is available at:

    http://www.danga.com/memcached/


pkgId: 1dc2a2f40b05bbb997bb7945a8c9dabad22019dc49ca1da5a487ae1582b4066c
name: local-perl-Cache-Memcached-Fast
arch: x86_64
version: 0.19
epoch: 0
release: 1
summary: Cache-Memcached-Fast - Perl client for B<memcached>, in C language
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tomash Brechko <tomash.brechko@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Cache-Memcached-Fast-0.19-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Cache-Memcached-Fast-0.19-1.x86_64.rpm
checksum_type: sha256
description:
  B<Cache::Memcahced::Fast> is a Perl client for B<memcached>, a memory
  cache daemon (L<http://www.danga.com/memcached/>).  Module core is
  implemented in C and tries hard to minimize number of system calls and
  to avoid any key/value copying for speed.  As a result, it has very
  low CPU consumption.

  API is largely compatible with L<Cache::Memcached|Cache::Memcached>,
  original pure Perl client, most users of the original module may start
  using this module by installing it and adding I<"::Fast"> to the old
  name in their scripts (see L</"Compatibility with Cache::Memcached">
  below for full details).


pkgId: 76b2cb3f415554fe1d7ee551e0cbac21733a5d9d4d0e745cbd2a78beb560d443
name: local-perl-Carp-Clan
arch: noarch
version: 6.04
epoch: 0
release: 1
summary: Carp-Clan - Report errors from perspective of caller of a "clan" of modules
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Steffen Beyer <STBEY@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Carp-Clan-6.04-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Carp-Clan-6.04-1.noarch.rpm
checksum_type: sha256
description:
  This module is based on "C<Carp.pm>" from Perl 5.005_03. It has been
  modified to skip all package names matching the pattern given in
  the "use" statement inside the "C<qw()>" term (or argument list).

  Suppose you have a family of modules or classes named "Pack::A",
  "Pack::B" and so on, and each of them uses "C<Carp::Clan qw(^Pack::);>"
  (or at least the one in which the error or warning gets raised).

  Thus when for example your script "tool.pl" calls module "Pack::A",
  and module "Pack::A" calls module "Pack::B", an exception raised in
  module "Pack::B" will appear to have originated in "tool.pl" where
  "Pack::A" was called, and not in "Pack::A" where "Pack::B" was called,
  as the unmodified "C<Carp.pm>" would try to make you believe C<:-)>.

  This works similarly if "Pack::B" calls "Pack::C" where the
  exception is raised, etcetera.

  In other words, this blames all errors in the "C<Pack::*>" modules
  on the user of these modules, i.e., on you. C<;-)>

  The skipping of a clan (or family) of packages according to a pattern
  describing its members is necessary in cases where these modules are
  not classes derived from each other (and thus when examining C<@ISA>
  - as in the original "C<Carp.pm>" module - doesn't help).

  The purpose and advantage of this is that a "clan" of modules can work
  together (and call each other) and throw exceptions at various depths
  down the calling hierarchy and still appear as a monolithic block (as
  though they were a single module) from the perspective of the caller.

  In case you just want to ward off all error messages from the module
  in which you "C<use Carp::Clan>", i.e., if you want to make all error
  messages or warnings to appear to originate from where your module
  was called (this is what you usually used to "C<use Carp;>" for C<;-)>),
  instead of in your module itself (which is what you can do with a
  "die" or "warn" anyway), you do not need to provide a pattern,
  the module will automatically provide the correct one for you.

  I.e., just "C<use Carp::Clan;>" without any arguments and call "carp"
  or "croak" as appropriate, and they will automatically defend your
  module against all blames!

  In other words, a pattern is only necessary if you want to make
  several modules (more than one) work together and appear as though
  they were only one.


pkgId: ec1576c1f32109eb6bb07c584cb4b1ab58db6f18f27cd397473262964df9602f
name: local-perl-Class-Accessor
arch: noarch
version: 0.34
epoch: 0
release: 1
summary: Class-Accessor - Automated accessor generation
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Marty Pauley <marty+perl@kasei.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Class-Accessor-0.34-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Class-Accessor-0.34-1.noarch.rpm
checksum_type: sha256
description:
  This module automagically generates accessors/mutators for your class.

  Most of the time, writing accessors is an exercise in cutting and
  pasting.  You usually wind up with a series of methods like this:

      sub name {
          my $self = shift;
          if(@_) {
              $self->{name} = $_[0];
          }
          return $self->{name};
      }

      sub salary {
          my $self = shift;
          if(@_) {
              $self->{salary} = $_[0];
          }
          return $self->{salary};
      }

    

  One for each piece of data in your object.  While some will be unique,
  doing value checks and special storage tricks, most will simply be
  exercises in repetition.  Not only is it Bad Style to have a bunch of
  repetitious code, but it's also simply not lazy, which is the real
  tragedy.

  If you make your module a subclass of Class::Accessor and declare your
  accessor fields with mk_accessors() then you'll find yourself with a
  set of automatically generated accessors which can even be
  customized!

  The basic set up is very simple:

      package Foo;
      use base qw(Class::Accessor);
      Foo->mk_accessors( qw(far bar car) );

  Done.  Foo now has simple far(), bar() and car() accessors
  defined.

  Alternatively, if you want to follow Damian's I<best practice> guidelines
  you can use:

      package Foo;
      use base qw(Class::Accessor);
      Foo->follow_best_practice;
      Foo->mk_accessors( qw(far bar car) );

  B<Note:> you must call C<follow_best_practice> before calling C<mk_accessors>.


pkgId: 4a841b7d296fea50a6da6aabb168f2ea9366078831feee20fc5f1c50e22be773
name: local-perl-Class-C3
arch: noarch
version: 0.23
epoch: 0
release: 1
summary: Class-C3 - A pragma to use the C3 method resolution order algortihm
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Stevan Little, <stevan@iinteractive.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Class-C3-0.23-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Class-C3-0.23-1.noarch.rpm
checksum_type: sha256
description:
  This is pragma to change Perl 5's standard method resolution order from depth-first left-to-right
  (a.k.a - pre-order) to the more sophisticated C3 method resolution order.

  B<NOTE:> YOU SHOULD NOT USE THIS MODULE DIRECTLY - The feature provided
  is integrated into perl version >= 5.9.5, and you should use L<MRO::Compat>
  instead, which will use the core implementation in newer perls, but fallback
  to using this implementation on older perls.


pkgId: 32a66fdc75af08c20f2386dbb034263283d8f1311f7afebfcc038c083325a644
name: local-perl-Class-Data-Inheritable
arch: noarch
version: 0.08
epoch: 0
release: 1
summary: Class-Data-Inheritable - Inheritable, overridable class data
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Original code by <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Class-Data-Inheritable-0.08-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Class-Data-Inheritable-0.08-1.noarch.rpm
checksum_type: sha256
description:
  Class::Data::Inheritable is for creating accessor/mutators to class
  data.  That is, if you want to store something about your class as a
  whole (instead of about a single object).  This data is then inherited
  by your subclasses and can be overriden.

  For example:

    Pere::Ubu->mk_classdata('Suitcase');

  will generate the method Suitcase() in the class Pere::Ubu.

  This new method can be used to get and set a piece of class data.

    Pere::Ubu->Suitcase('Red');
    $suitcase = Pere::Ubu->Suitcase;

  The interesting part happens when a class inherits from Pere::Ubu:

    package Raygun;
    use base qw(Pere::Ubu);

    
    $suitcase = Raygun->Suitcase;

  Raygun inherits its Suitcase class data from Pere::Ubu.

  Inheritance of class data works analogous to method inheritance.  As
  long as Raygun does not "override" its inherited class data (by using
  Suitcase() to set a new value) it will continue to use whatever is set
  in Pere::Ubu and inherit further changes:

    
    Pere::Ubu->Suitcase('Blue');

  However, should Raygun decide to set its own Suitcase() it has now
  "overridden" Pere::Ubu and is on its own, just like if it had
  overriden a method:

    
    Raygun->Suitcase('Orange');

  Now that Raygun has overridden Pere::Ubu futher changes by Pere::Ubu
  no longer effect Raygun.

    
    Pere::Ubu->Suitcase('Samsonite');


pkgId: 5171b28f8a1089c5b9feb80bcaa14c0b4c37f1102c0227621a8fcb399f1dbc36
name: local-perl-Class-ISA
arch: noarch
version: 0.36
epoch: 0
release: 1
summary: Class-ISA - report the search path for a class's ISA tree
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sean M Burke <Csburke@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Class-ISA-0.36-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Class-ISA-0.36-1.noarch.rpm
checksum_type: sha256
description:
  Suppose you have a class (like Food::Fish::Fishstick) that is derived,
  via its @ISA, from one or more superclasses (as Food::Fish::Fishstick
  is from Food::Fish, Life::Fungus, and Chemicals), and some of those
  superclasses may themselves each be derived, via its @ISA, from one or
  more superclasses (as above).

  When, then, you call a method in that class ($fishstick->calories),
  Perl first searches there for that method, but if it's not there, it
  goes searching in its superclasses, and so on, in a depth-first (or
  maybe "height-first" is the word) search.  In the above example, it'd
  first look in Food::Fish, then Food, then Matter, then Life::Fungus,
  then Life, then Chemicals.

  This library, Class::ISA, provides functions that return that list --
  the list (in order) of names of classes Perl would search to find a
  method, with no duplicates.


pkgId: ec0e72d86dfdaef1f327c38aa6d571c4b86ccc89f62b0889394512ef4dbb8851
name: local-perl-Class-Method-Modifiers
arch: noarch
version: 1.08
epoch: 0
release: 1
summary: Class-Method-Modifiers - provides Moose-like method modifiers
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Shawn M Moore, C<sartak@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Class-Method-Modifiers-1.08-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Class-Method-Modifiers-1.08-1.noarch.rpm
checksum_type: sha256
description:
  Method modifiers are a convenient feature from the CLOS (Common Lisp Object
  System) world.

  In its most basic form, a method modifier is just a method that calls
  C<< $self->SUPER::foo(@_) >>. I for one have trouble remembering that exact
  invocation, so my classes seldom re-dispatch to their base classes. Very bad!

  C<Class::Method::Modifiers> provides three modifiers: C<before>, C<around>, and
  C<after>. C<before> and C<after> are run just before and after the method they
  modify, but can not really affect that original method. C<around> is run in
  place of the original method, with a hook to easily call that original method.
  See the C<MODIFIERS> section for more details on how the particular modifiers
  work.

  One clear benefit of using C<Class::Method::Modifiers> is that you can define
  multiple modifiers in a single namespace. These separate modifiers don't need
  to know about each other. This makes top-down design easy. Have a base class
  that provides the skeleton methods of each operation, and have plugins modify
  those methods to flesh out the specifics.

  Parent classes need not know about C<Class::Method::Modifiers>. This means you
  should be able to modify methods in I<any> subclass. See
  L<Term::VT102::ZeroBased> for an example of subclassing with CMM.

  In short, C<Class::Method::Modifiers> solves the problem of making sure you
  call C<< $self->SUPER::foo(@_) >>, and provides a cleaner interface for it.

  As of version 1.00, C<Class::Method::Modifiers> is faster in some cases than
  L<Moose>. See C<benchmark/method_modifiers.pl> in the L<Moose> distribution.


pkgId: fa19fb488e9eea842993ba1a1bd1a62b2e10cfebd92519866378f6f4c09fa92a
name: local-perl-Class-Singleton
arch: noarch
version: 1.4
epoch: 0
release: 1
summary: Class-Singleton - Base class for creating singleton objects
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Wardley <abw@wardley.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Class-Singleton-1.4-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Class-Singleton-1.4-1.noarch.rpm
checksum_type: sha256
description:
  This is the C<Class::Singleton> module.  A Singleton describes an object class
  that can have only one instance in any system.  An example of a Singleton
  might be a print spooler or system registry.  This module implements a
  Singleton class from which other classes can be derived.  By itself, the
  C<Class::Singleton> module does very little other than manage the instantiation
  of a single object.  In deriving a class from C<Class::Singleton>, your module
  will inherit the Singleton instantiation method and can implement whatever
  specific functionality is required.

  For a description and discussion of the Singleton class, see
  "Design Patterns", Gamma et al, Addison-Wesley, 1995, ISBN 0-201-63361-2.


pkgId: 05c76aaaa5328457c3d75170d37d21bcf766e0beb049424f74560e7e8e73d369
name: local-perl-Clone
arch: x86_64
version: 0.31
epoch: 0
release: 1
summary: Clone - recursively copy Perl datatypes
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ray Finch <rdf@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Clone-0.31-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Clone-0.31-1.x86_64.rpm
checksum_type: sha256
description:
  This module provides a clone() method which makes recursive
  copies of nested hash, array, scalar and reference types,
  including tied variables and objects.


  clone() takes a scalar argument and an optional parameter that
  can be used to limit the depth of the copy. To duplicate lists,
  arrays or hashes, pass them in by reference. e.g.

      my $copy = clone (\@array);

      

      my %copy = %;


  For a slower, but more flexible solution see Storable's dclone().


pkgId: c523da390092399b47126a430bed51748cbd09f2b0eab21923bf63df2e4fc363
name: local-perl-Compress-Raw-Bzip2
arch: x86_64
version: 2.037
epoch: 0
release: 1
summary: Compress-Raw-Bzip2 - Low-Level Interface to bzip2 compression library
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Paul Marquess <pmqs@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Compress-Raw-Bzip2-2.037-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Compress-Raw-Bzip2-2.037-1.x86_64.rpm
checksum_type: sha256
description:
  C<Compress::Raw::Bzip2> provides an interface to the in-memory
  compression/uncompression functions from the bzip2 compression library.

  Although the primary purpose for the existence of C<Compress::Raw::Bzip2>
  is for use by the  C<IO::Compress::Bzip2> and C<IO::Compress::Bunzip2>
  modules, it can be used on its own for simple compression/uncompression
  tasks.


pkgId: 630d85d90f91df1a1fbbb9069f3966523cbaf79b1a7353078b63ed0e25e2ab45
name: local-perl-Compress-Raw-Zlib
arch: x86_64
version: 2.033
epoch: 0
release: 162.ep
summary: Low-Level Interface to the zlib compression library
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Compress-Raw-Zlib-2.033-162.ep.x86_64.rpm
checksum_type: sha256
description:
  This module provides a Perl interface to the zlib compression library.
  It is used by IO::Compress::Zlib.


pkgId: 820fa50026a52a41ddbe4389007ed8a3b6a59eb95705ea85d0753b5b5354fc2c
name: local-perl-Compress-Raw-Zlib
arch: x86_64
version: 2.037
epoch: 0
release: 1
summary: Compress-Raw-Zlib - Low-Level Interface to zlib compression library
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: by Paul Marquess <Fpmqs@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Compress-Raw-Zlib-2.037-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Compress-Raw-Zlib-2.037-1.x86_64.rpm
checksum_type: sha256
description:
  The I<Compress::Raw::Zlib> module provides a Perl interface to the I<zlib>
  compression library (see L</AUTHOR> for details about where to get
  I<zlib>).


pkgId: a318c5ab05fe3c39be6347c71c1a641545ebe5f393b9b88ad4acf2c34b509039
name: local-perl-Config-YAML
arch: noarch
version: 1.42
epoch: 0
release: 1
summary: Config-YAML - Simple configuration automation
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Shawn Boyette <mdxi@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Config-YAML-1.42-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Config-YAML-1.42-1.noarch.rpm
checksum_type: sha256
description:
  Config::YAML is a somewhat object-oriented wrapper around the YAML
  module which makes reading and writing configuration files
  simple. Handling multiple config files (e.g. system and per-user
  configuration, or a gallery app with per-directory configuration) is a
  snap.

      use Config::YAML;

      
      
      my $c = Config::YAML->new( config => "/usr/share/foo/globalconf",
                                 output => "~/.foorc",
                                 param1 => value1,
                                 param2 => value2,
                                 ...
                                 paramN => valueN,
                               );

      
      $c->read("~/.foorc");

      
      $rc = GetOptions ( $c,
                         'param1|p!',
                         'param2|P',
                         'paramN|n',
                       );

      
      $c->write;

      
      do_something() unless $c->{param1};
      
      my $value = $c->get_param2;


pkgId: a25178af61c1be1dee181cb10698ec3ec7ac14cc1eb07fe9821ab1c6677e4d59
name: local-perl-Crypt-Blowfish
arch: x86_64
version: 2.12
epoch: 0
release: 1
summary: Crypt-Blowfish - Perl Blowfish encryption module
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: dparis@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Crypt-Blowfish-2.12-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Crypt-Blowfish-2.12-1.x86_64.rpm
checksum_type: sha256
description:
  Blowfish is capable of strong encryption and can use key sizes up
  to 56 bytes (a 448 bit key).  You're encouraged to take advantage
  of the full key size to ensure the strongest encryption possible
  from this module.

  Crypt::Blowfish has the following methods:

  =over 4

   blocksize()
   keysize()
   encrypt()
   decrypt()

  =back


pkgId: 6617248aa7d51b167c593b9a2899b098b20e3fbba81b0b8044cac672d06958ab
name: local-perl-Crypt-OpenSSL-RSA
arch: x86_64
version: 0.28
epoch: 0
release: 1
summary: Crypt-OpenSSL-RSA - RSA encoding and decoding, using the openSSL libraries
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ian Robertson <iroberts@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Crypt-OpenSSL-RSA-0.28-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Crypt-OpenSSL-RSA-0.28-1.x86_64.rpm
checksum_type: sha256
description:
  Crypt::OpenSSL::RSA provides the ability to RSA encrypt strings which are
  somewhat shorter than the block size of a key.  It also allows for decryption,
  signatures and signature verification.

  I<NOTE>: Many of the methods in this package can croak, so use eval, or
  Error.pm's try/catch mechanism to capture errors.  Also, while some
  methods from earlier versions of this package return true on success,
  this (never documented) behavior is no longer the case.


pkgId: e8ff44ebc03ca5aaf93668a99712ec55c864eede6521835bf440c65f38a41a29
name: local-perl-Crypt-OpenSSL-Random
arch: x86_64
version: 0.04
epoch: 0
release: 1
summary: Crypt-OpenSSL-Random - RSA encoding and decoding, using the openSSL libraries
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ian Robertson <iroberts@cpan.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Crypt-OpenSSL-Random-0.04-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Crypt-OpenSSL-Random-0.04-1.x86_64.rpm
checksum_type: sha256
description:
  Crypt::OpenSSL::Random provides the ability to seed and query the
  OpenSSL library's pseudo-random number generator


pkgId: e0a5ae37735e4c845786861626987a6e27026432c9d19bcd9ab9c71cfc9b06d4
name: local-perl-Crypt-PasswdMD5
arch: noarch
version: 1.3
epoch: 0
release: 1
summary: Crypt-PasswdMD5 - Provides interoperable MD5-based crypt() functions
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Luis E. Muñoz <luismunoz@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Crypt-PasswdMD5-1.3-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Crypt-PasswdMD5-1.3-1.noarch.rpm
checksum_type: sha256
description:
  the C<unix_md5_crypt()> provides a crypt()-compatible interface to the
  rather new MD5-based crypt() function found in modern operating systems.
  It's based on the implementation found on FreeBSD 2.2.[56]-RELEASE and
  contains the following license in it:

   "THE BEER-WARE LICENSE" (Revision 42):
   <phk@login.dknet.dk> wrote this file.  As long as you retain this notice you
   can do whatever you want with this stuff. If we meet some day, and you think
   this stuff is worth it, you can buy me a beer in return.   Poul-Henning Kamp

  C<apache_md5_crypt()> provides a function compatible with Apache's
  C<.htpasswd> files. This was contributed by Bryan Hart <bryan@eai.com>.
  As suggested by William A. Rowe, Jr. <wrowe@lnd.com>, it is
  exported by default.

  For both functions, if a salt value is not supplied, a random salt will be
  generated.  Contributed by John Peacock <jpeacock@cpan.org>.


pkgId: 8737fea575256752b819cf5b6615ac96813bded984c9f76d9b47d49e5351d6d6
name: local-perl-Crypt-RC4
arch: noarch
version: 2.02
epoch: 0
release: 1
summary: Crypt-RC4 - Perl implementation of the RC4 encryption algorithm
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Kurt Kincaid <sifukurt@yahoo.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Crypt-RC4-2.02-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Crypt-RC4-2.02-1.noarch.rpm
checksum_type: sha256
description:
  A simple implementation of the RC4 algorithm, developed by RSA Security, Inc. Here is the description
  from RSA's website:

  RC4 is a stream cipher designed by Rivest for RSA Data Security (now RSA Security). It is a variable
  key-size stream cipher with byte-oriented operations. The algorithm is based on the use of a random
  permutation. Analysis shows that the period of the cipher is overwhelmingly likely to be greater than
  10100. Eight to sixteen machine operations are required per output byte, and the cipher can be
  expected to run very quickly in software. Independent analysts have scrutinized the algorithm and it
  is considered secure.

  Based substantially on the "RC4 in 3 lines of perl" found at http://www.cypherspace.org

  A major bug in v1.0 was fixed by David Hook (dgh@wumpus.com.au).  Thanks, David.


pkgId: 00cb3ecfa508ea0a9662711e38385b03491775cb2b42fb90ca6c02de3af9eef6
name: local-perl-Crypt-SSLeay
arch: x86_64
version: 0.58_01
epoch: 0
release: 1
summary: Crypt-SSLeay - OpenSSL support for LWP
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: A. Sinan Unur <nanis@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Crypt-SSLeay-0.58_01-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Crypt-SSLeay-0.58_01-1.x86_64.rpm
checksum_type: sha256
description:
  This Perl module provides support for the HTTPS protocol under LWP,
  to allow an C<LWP::UserAgent> object to perform GET, HEAD and POST
  requests. Please see LWP for more information on POST requests.

  The C<Crypt::SSLeay> package provides C<Net::SSL>, which is loaded
  by C<LWP::Protocol::https> for https requests and provides the
  necessary SSL glue.

  This distribution also makes following deprecated modules available:

      Crypt::SSLeay::CTX
      Crypt::SSLeay::Conn
      Crypt::SSLeay::X509

  Work on Crypt::SSLeay has been continued only to provide https
  support for the LWP (libwww-perl) libraries.


pkgId: 1124033115e458bc1b4fdff079c0dc35d8d28ef77a5c1ddedc27232458bdf86f
name: local-perl-DBD-mysql
arch: x86_64
version: 4.019
epoch: 0
release: 1
summary: DBD-mysql - A MySQL driver for the Perl5 Database Interface (DBI)
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Rudy Lippan <rlippan@remotelinux.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-DBD-mysql-4.019-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-DBD-mysql-4.019-1.x86_64.rpm
checksum_type: sha256
description:
  B<DBD::mysql> is the Perl5 Database Interface driver for the MySQL
  database. In other words: DBD::mysql is an interface between the Perl
  programming language and the MySQL programming API that comes with
  the MySQL relational database management system. Most functions
  provided by this programming API are supported. Some rarely used
  functions are missing, mainly because noone ever requested
  them. :-)

  In what follows we first discuss the use of DBD::mysql,
  because this is what you will need the most. For installation, see the
  sections on L<INSTALLATION>, and L<WIN32 INSTALLATION>
  below. See L<EXAMPLE> for a simple example above.

  From perl you activate the interface with the statement

      use DBI;

  After that you can connect to multiple MySQL database servers
  and send multiple queries to any of them via a simple object oriented
  interface. Two types of objects are available: database handles and
  statement handles. Perl returns a database handle to the connect
  method like so:

    $dbh = DBI->connect("DBI:mysql:database=$db;host=$host",
  		      $user, $password, {RaiseError => 1});

  Once you have connected to a database, you can can execute SQL
  statements with:

    my $query = sprintf("INSERT INTO foo VALUES (%d, %s)",
  		      $number, $dbh->quote("name"));
    $dbh->do($query);

  See L<DBI(3)> for details on the quote and do methods. An alternative
  approach is

    $dbh->do("INSERT INTO foo VALUES (?, ?)", undef,
  	   $number, $name);

  in which case the quote method is executed automatically. See also
  the bind_param method in L<DBI(3)>. See L<DATABASE HANDLES> below
  for more details on database handles.

  If you want to retrieve results, you need to create a so-called
  statement handle with:

    $sth = $dbh->prepare("SELECT * FROM $table");
    $sth->execute();

  This statement handle can be used for multiple things. First of all
  you can retreive a row of data:

    my $row = $sth->fetchrow_hashref();

  If your table has columns ID and NAME, then $row will be hash ref with
  keys ID and NAME. See L<STATEMENT HANDLES> below for more details on
  statement handles.

  But now for a more formal approach:


pkgId: e92e87f6f020a20cb02c84dfe0f32bf54caa27a9f1148599a995dd8d4e35224e
name: local-perl-DBI
arch: x86_64
version: 1.616
epoch: 0
release: 1
summary: DBI - Database independent interface for Perl
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tim Bunce (dbi-users@perl.org)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-DBI-1.616-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-DBI-1.616-1.x86_64.rpm
checksum_type: sha256
description:
  The DBI is a database access module for the Perl programming language.  It defines
  a set of methods, variables, and conventions that provide a consistent
  database interface, independent of the actual database being used.

  It is important to remember that the DBI is just an interface.
  The DBI is a layer
  of "glue" between an application and one or more database I<driver>
  modules.  It is the driver modules which do most of the real work. The DBI
  provides a standard interface and framework for the drivers to operate
  within.


pkgId: 7d99aabc35c26af7c88dc56e93ad15591a9e5accb8d6def874b203db0e54987f
name: local-perl-DBIx-Safe
arch: noarch
version: 1.2.5
epoch: 0
release: 1
summary: DBIx-Safe - Safe wrapper to DBI interface
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Greg Sabino Mullane <greg@endpoint.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-DBIx-Safe-1.2.5-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-DBIx-Safe-1.2.5-1.noarch.rpm
checksum_type: sha256
description:
  The purpose of this module is to give controlled, limited access to an application,
  rather than simply passing it a raw database handle through DBI. DBIx::Safe acts as
  a wrapper to the database, by only allowing through the commands you tell it to. It
  filters all things related to the database handle - methods and attributes.

  The typical usage is for your application to create a database handle via a normal
  DBI call to new(), then pass that to DBIx::Safe->new(), which will return you a
  DBIx::Safe object. After specifying exactly what is and what is not allowed, you can
  pass the object to the untrusted application. The object will act very similar to a
  DBI database handle, and in most cases can be used interchangeably.

  By default, nothing is allowed to run at all. There are many things you can control.
  You can specify which SQL commands are allowed, by indicating the first word in the
  SQL statement (e.g. 'SELECT'). You can specify which database methods are allowed to
  run (e.g. 'ping'). You can specify a regular expression that allows matching SQL
  statements to run (e.g. 'qr{SET TIMEZONE}'). You can specify a regular expression
  that is NOT allowed to run (e.g. qr(UPDATE xxx}). Finally, you can indicate which
  database attributes are allowed to be read and changed (e.g. 'PrintError'). For all
  of the above, there are matching methods to remove them as well.


pkgId: 38397970cbd30d64d2dc0b2a2e84af7c0a31e38b7c5170e97cb7ce69914f5041
name: local-perl-Dancer
arch: noarch
version: 1.3090
epoch: 0
release: 1
summary: Dancer - A minimal-effort oriented web application framework
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: by Alexis Sukrieh <sukria@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Dancer-1.3090-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Dancer-1.3090-1.noarch.rpm
checksum_type: sha256
description:
  Dancer is a web application framework designed to be as effortless as possible
  for the developer, taking care of the boring bits as easily as possible, yet
  staying out of your way and letting you get on with writing your code.

  Dancer aims to provide the simplest way for writing web applications, and
  offers the flexibility to scale between a very simple lightweight web service
  consisting of a few lines of code in a single file, all the way up to a more
  complex fully-fledged web application with session support, templates for views
  and layouts, etc.

  If you don't want to write CGI scripts by hand, and find Catalyst too big or
  cumbersome for your project, Dancer is what you need.

  Dancer has few pre-requisites, so your Dancer webapps will be easy to deploy.

  Dancer apps can be used with a an embedded web server (great for easy testing),
  and can run under PSGI/Plack for easy deployment in a variety of webserver
  environments.


pkgId: 4acf12c60624f192373726b3a4db564184fe642176176c1cbbe967fc1dde28c3
name: local-perl-Data-Dump
arch: noarch
version: 1.21
epoch: 0
release: 1
summary: Data-Dump - Pretty printing of data structures
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Data-Dump-1.21-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Data-Dump-1.21-1.noarch.rpm
checksum_type: sha256
description:
  This module provide a few functions that traverse their
  argument and produces a string as its result.  The string contains
  Perl code that, when C<eval>ed, produces a deep copy of the original
  arguments.

  The main feature of the module is that it strives to produce output
  that is easy to read.  Example:

      @a = (1, [2, 3], {4 => 5});
      dump(@a);

  Produces:

      "(1, [2, 3], { 4 => 5 })"

  If you dump just a little data, it is output on a single line. If
  you dump data that is more complex or there is a lot of it, line breaks
  are automatically added to keep it easy to read.

  The following functions are provided (only the dd* functions are exported by default):

  =over

  =item dump( ... )

  =item pp( ... )

  Returns a string containing a Perl expression.  If you pass this
  string to Perl's built-in eval() function it should return a copy of
  the arguments you passed to dump().

  If you call the function with multiple arguments then the output will
  be wrapped in parenthesis "( ..., ... )".  If you call the function with a
  single argument the output will not have the wrapping.  If you call the function with
  a single scalar (non-reference) argument it will just return the
  scalar quoted if needed, but never break it into multiple lines.  If you
  pass multiple arguments or references to arrays of hashes then the
  return value might contain line breaks to format it for easier
  reading.  The returned string will never be "\n" terminated, even if
  contains multiple lines.  This allows code like this to place the
  semicolon in the expected place:

     print '$obj = ', dump($obj), ";\n";

  If dump() is called in void context, then the dump is printed on
  STDERR and then "\n" terminated.  You might find this useful for quick
  debug printouts, but the dd*() functions might be better alternatives
  for this.

  There is no difference between dump() and pp(), except that dump()
  shares its name with a not-so-useful perl builtin.  Because of this
  some might want to avoid using that name.

  =item quote( $string )

  Returns a quoted version of the provided string.

  It differs from C<dump($string)> in that it will quote even numbers and
  not try to come up with clever expressions that might shorten the
  output.  If a non-scalar argument is provided then it's just stringified
  instead of traversed.

  =item dd( ... )

  =item ddx( ... )

  These functions will call dump() on their argument and print the
  result to STDOUT (actually, it's the currently selected output handle, but
  STDOUT is the default for that).

  The difference between them is only that ddx() will prefix the lines
  it prints with "# " and mark the first line with the file and line
  number where it was called.  This is meant to be useful for debug
  printouts of state within programs.

  =item dumpf( ..., \&filter )

  Short hand for calling the dump_filtered() function of L<Data::Dump::Filtered>.
  This works like dump(), but the last argument should be a filter callback
  function.  As objects are visited the filter callback is invoked and it
  can modify how the objects are dumped.

  =back


pkgId: 853abcb7cc649807f59c703c7ce479b25ddaec6e16d667254e5d5a6d743a8e8d
name: local-perl-Data-HashArray
arch: noarch
version: 1.0
epoch: 0
release: 1
summary: Data-HashArray - An array class of hashes that has magical properties via overloading and AUTOLOAD.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ayhan Ulusoy <dev@ulusoy.name>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Data-HashArray-1.0-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Data-HashArray-1.0-1.noarch.rpm
checksum_type: sha256
description:
  Normally, B<Data::HashArray> is an array of hashes or hash-based objects. This class has some magical properties
  that make it easier to deal with multiplicity.

  First, there exist two B<overload>s. One for hash access and the other for stringification. Both will act on the first
  element of the array. In other words, performing a hash access on an object of this class will be equivalent to
  performing a hash access on the first element of the array.

  Second, the AUTOLOAD method will delegate any method unkown to this class to the first item in the array as well. For this to
  work, at least the first item of the array better be an object on which one could call such a method.

  Both of these magical properties make it easier to deal with unpredictable multiplicity. You can both treat the object as an array
  or as hash (the first one in the array). This way, if your code deosn't know that an element can occur multiple times (in other words, if the
  code treats the element as singular), the same code should still largely work when the singualr element is replaced by a B<Data::HashArray> object.

  The other practical feature of this class is the capabality to place the objects (or hashes) in the array into a hash keyed on the value of a given field or fields
  (see the L</hash()> method for further details).


pkgId: 8e5f321810df69575aa745e6188550ef3e4611d21bdceb2cd820d3dca410f0c0
name: local-perl-Data-Peek
arch: x86_64
version: 0.33
epoch: 0
release: 1
summary: Data-Peek - Extended/Modified debugging utilities
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: H.Merijn Brand <h.merijn@xs4all.nl>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Data-Peek-0.33-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Data-Peek-0.33-1.x86_64.rpm
checksum_type: sha256
description:
  Data::Peek started off as C<DDumper> being a wrapper module over
  L<Data::Dumper>, but grew out to be a set of low-level data
  introspection utilities that no other module provided yet, using the
  lowest level of the perl internals API as possible.


pkgId: 3fb5545506455d8303cd03438ec7e140c763151cd2ad0d306e08a559032d5a46
name: local-perl-Data-UUID
arch: x86_64
version: 1.221
epoch: 0
release: 1
summary: Data-UUID - Globally/Universally Unique Identifiers (GUIDs/UUIDs)
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ricardo Signes <rjbs[at]cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Data-UUID-1.221-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Data-UUID-1.221-1.x86_64.rpm
checksum_type: sha256
description:
  This module provides a framework for generating v3 UUIDs (Universally Unique
  Identifiers, also known as GUIDs (Globally Unique Identifiers). A UUID is 128
  bits long, and is guaranteed to be different from all other UUIDs/GUIDs
  generated until 3400 CE.

  UUIDs were originally used in the Network Computing System (NCS) and later in
  the Open Software Foundation's (OSF) Distributed Computing Environment.
  Currently many different technologies rely on UUIDs to provide unique identity
  for various software components. Microsoft COM/DCOM for instance, uses GUIDs
  very extensively to uniquely identify classes, applications and components
  across network-connected systems.

  The algorithm for UUID generation, used by this extension, is described in the
  Internet Draft "UUIDs and GUIDs" by Paul J. Leach and Rich Salz.  (See RFC
  4122.)  It provides reasonably efficient and reliable framework for generating
  UUIDs and supports fairly high allocation rates -- 10 million per second per
  machine -- and therefore is suitable for identifying both extremely short-lived
  and very persistent objects on a given system as well as across the network.

  This modules provides several methods to create a UUID.  In all methods, C<<
  <namespace> >> is a UUID and C<< <name> >> is a free form string.

     
     $ug->create();
     $ug->create_bin();

     
     
     $ug->create_from_name(<namespace>, <name>);
     $ug->create_from_name_bin(<namespace>, <name>);

     
     
     
     $ug->create_str();
     $ug->create_from_name_str(<namespace>, <name>);

     
     
     
     $ug->create_hex();
     $ug->create_from_name_hex(<namespace>, <name>);

     
     $ug->create_b64();
     $ug->create_from_name_b64(<namespace>, <name>);

     Binary UUIDs can be converted to printable strings using following methods:

     
     $ug->to_string(<uuid>);

     
     $ug->to_hexstring(<uuid>);

     
     $ug->to_b64string(<uuid>);

     Conversly, string UUIDs can be converted back to binary form:

     
     $ug->from_string(<uuid>);
     $ug->from_hexstring(<uuid>);

     
     $ug->from_b64string(<uuid>);

     Finally, two binary UUIDs can be compared using the following method:

     
     
     $ug->compare(<uuid1>, <uuid2>);

  Examples:

     use Data::UUID;

     
     

     $ug = Data::UUID->new;
     print $ug->create_from_name_str(NameSpace_URL, "www.mycompany.com");


pkgId: 436a53db790043b1260f99b7a93defe54ff81f7eb22defdc423270061af16318
name: local-perl-Data-Visitor
arch: noarch
version: 0.27
epoch: 0
release: 1
summary: Data-Visitor - Visitor style traversal of Perl data structures
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Yuval Kogman C <nothingmuch@woobling.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Data-Visitor-0.27-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Data-Visitor-0.27-1.noarch.rpm
checksum_type: sha256
description:
  This module is a simple visitor implementation for Perl values.

  It has a main dispatcher method, C<visit>, which takes a single perl value and
  then calls the methods appropriate for that value.

  It can recursively map (cloning as necessary) or just traverse most structures,
  with support for per object behavior, circular structures, visiting tied
  structures, and all ref types (hashes, arrays, scalars, code, globs).

  L<Data::Visitor> is meant to be subclassed, but also ships with a callback
  driven subclass, L<Data::Visitor::Callback>.


pkgId: ff6fd6207145c165660bb72578b227caa6afb6d70a03ee1248dc00978bc7d3a9
name: local-perl-Date-Calc
arch: noarch
version: 6.3
epoch: 0
release: 1
summary: Date-Calc - Gregorian calendar date calculations
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Steffen Beyer <STBEY@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Date-Calc-6.3-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Date-Calc-6.3-1.noarch.rpm
checksum_type: sha256
description:
  =over 2

  =item *

  C<use Date::Calc qw( Days_in_Year Days_in_Month ... );>

  =item *

  C<use Date::Calc qw(:all);>

  You can either specify the functions you want to import explicitly by
  enumerating them between the parentheses of the "C<qw()>" operator, or
  you can use the "C<:all>" tag instead to import B<ALL> available functions.

  =item *

  C<$days = Days_in_Year($year,$month);>

  This function returns the sum of the number of days in the months starting
  with January up to and including "C<$month>" in the given year "C<$year>".

  I.e., "C<Days_in_Year(1998,1)>" returns "C<31>", "C<Days_in_Year(1998,2)>"
  returns "C<59>", "C<Days_in_Year(1998,3)>" returns "C<90>", and so on.

  Note that "C<Days_in_Year($year,12)>" returns the number of days in the
  given year "C<$year>", i.e., either "C<365>" or "C<366>".

  =item *

  C<$days = Days_in_Month($year,$month);>

  This function returns the number of days in the given month "C<$month>" of
  the given year "C<$year>".

  The year must always be supplied, even though it is only needed when the
  month is February, in order to determine whether it is a leap year or not.

  I.e., "C<Days_in_Month(1998,1)>" returns "C<31>", "C<Days_in_Month(1998,2)>"
  returns "C<28>", "C<Days_in_Month(2000,2)>" returns "C<29>",
  "C<Days_in_Month(1998,3)>" returns "C<31>", and so on.

  =item *

  C<$weeks = Weeks_in_Year($year);>

  This function returns the number of weeks in the given year "C<$year>",
  i.e., either "C<52>" or "C<53>".

  =item *

  C<if (leap_year($year))>

  This function returns "true" ("C<1>") if the given year "C<$year>" is
  a leap year and "false" ("C<0>") otherwise.

  =item *

  C<if (check_date($year,$month,$day))>

  This function returns "true" ("C<1>") if the given three numerical
  values "C<$year>", "C<$month>" and "C<$day>" constitute a valid date,
  and "false" ("C<0>") otherwise.

  =item *

  C<if (check_time($hour,$min,$sec))>

  This function returns "true" ("C<1>") if the given three numerical
  values "C<$hour>", "C<$min>" and "C<$sec>" constitute a valid time
  (C<0 E<lt>= $hour E<lt> 24>, C<0 E<lt>= $min E<lt> 60> and
  C<0 E<lt>= $sec E<lt> 60>), and "false" ("C<0>") otherwise.

  =item *

  C<if (check_business_date($year,$week,$dow))>

  This function returns "true" ("C<1>") if the given three numerical
  values "C<$year>", "C<$week>" and "C<$dow>" constitute a valid date
  in business format, and "false" ("C<0>") otherwise.

  B<Beware> that this function does B<NOT> compute whether a given date
  is a business day (i.e., Monday to Friday)!

  To do so, use "C<(Day_of_Week($year,$month,$day) E<lt> 6)>" instead.

  =item *

  C<$doy = Day_of_Year($year,$month,$day);>

  This function returns the (relative) number of the day of the given date
  in the given year.

  E.g., "C<Day_of_Year($year,1,1)>" returns "C<1>",
  "C<Day_of_Year($year,2,1)>" returns "C<32>", and
  "C<Day_of_Year($year,12,31)>" returns either "C<365>" or "C<366>".

  The day of year is sometimes also referred to as the Julian day (or date),
  although it has nothing to do with the Julian calendar, the calendar which
  was used before the Gregorian calendar.

  In order to convert the number returned by this function back into a
  date, use the function "C<Add_Delta_Days()>" (described further below),
  as follows:

    $doy = Day_of_Year($year,$month,$day);
    ($year,$month,$day) = Add_Delta_Days($year,1,1, $doy - 1);

  =item *

  C<$days = Date_to_Days($year,$month,$day);>

  This function returns the (absolute) number of the day of the given date,
  where counting starts at the 1st of January of the year S<1 A.D.>

  I.e., "C<Date_to_Days(1,1,1)>" returns "C<1>", "C<Date_to_Days(1,12,31)>"
  returns "C<365>", "C<Date_to_Days(2,1,1)>" returns "C<366>",
  "C<Date_to_Days(1998,5,1)>" returns "C<729510>", and so on.

  This is sometimes also referred to (not quite correctly) as the Julian
  date (or day). This may cause confusion, because also the number of the
  day in a year (from 1 to 365 or 366) is frequently called the "Julian day".

  More confusing still, this has nothing to do with the Julian calendar,
  which was used B<BEFORE> the Gregorian calendar.

  The Julian calendar was named after famous Julius Caesar, who had
  instituted it in Roman times. The Julian calendar is less precise than
  the Gregorian calendar because it has too many leap years compared to
  the true mean length of a year (but the Gregorian calendar also still
  has one day too much every 5000 years). Anyway, the Julian calendar was
  better than what existed before, because rulers had often changed the
  calendar used until then in arbitrary ways, in order to lengthen their
  own reign, for instance.

  In order to convert the number returned by this function back into
  a date, use the function "C<Add_Delta_Days()>" (described further
  below), as follows:

    $days = Date_to_Days($year,$month,$day);
    ($year,$month,$day) = Add_Delta_Days(1,1,1, $days - 1);

  =item *

  C<$dow = Day_of_Week($year,$month,$day);>

  This function returns the number of the day of week of the given date.

  The function returns "C<1>" for Monday, "C<2>" for Tuesday and so on
  until "C<7>" for Sunday.

  Note that in the Hebrew calendar (on which the Christian calendar is based),
  the week starts with Sunday and ends with the Sabbath or Saturday (where
  according to the Genesis (as described in the Bible) the Lord rested from
  creating the world).

  In medieval times, Catholic Popes have decreed the Sunday to be the official
  day of rest, in order to dissociate the Christian from the Hebrew belief.

  It appears that this actually happened with the Emperor Constantin, who
  converted to Christianity but still worshipped the Sun god and therefore
  moved the Christian sabbath to the day of the Sun.

  Nowadays, the Sunday B<AND> the Saturday are commonly considered (and
  used as) days of rest, usually referred to as the "week-end".

  Consistent with this practice, current norms and standards (such as
  S<ISO/R 2015-1971>, S<DIN 1355> and S<ISO 8601>) define the Monday
  as the first day of the week.

  =item *

  C<$week = Week_Number($year,$month,$day);>

  This function returns the number of the week the given date lies in.

  If the given date lies in the B<LAST> week of the B<PREVIOUS> year,
  "C<0>" is returned.

  If the given date lies in the B<FIRST> week of the B<NEXT> year,
  "C<Weeks_in_Year($year) + 1>" is returned.

  =item *

  C<($week,$year) = Week_of_Year($year,$month,$day);>

  This function returns the number of the week the given date lies in,
  as well as the year that week belongs to.

  I.e., if the given date lies in the B<LAST> week of the B<PREVIOUS> year,
  "C<(Weeks_in_Year($year-1), $year-1)>" is returned.

  If the given date lies in the B<FIRST> week of the B<NEXT> year,
  "C<(1, $year+1)>" is returned.

  Otherwise, "C<(Week_Number($year,$month,$day), $year)>" is returned.

  =item *

  C<$week = Week_of_Year($year,$month,$day);>

  In scalar context, this function returns just the week number. This
  allows you to write "C<$week = Week_of_Year($year,$month,$day);>"
  instead of "C<($week) = Week_of_Year($year,$month,$day);>" (note
  the parentheses around "C<$week>").

  If the given date lies in the B<LAST> week of the B<PREVIOUS> year,
  "C<Weeks_in_Year($year-1)>" is returned.

  If the given date lies in the B<FIRST> week of the B<NEXT> year,
  "C<1>" is returned.

  Otherwise the return value is identical with that of
  "C<Week_Number($year,$month,$day)>".

  B<BEWARE> that using this function in scalar context is a B<DANGEROUS>
  feature, because without knowing which year the week belongs to, you
  might inadvertently assume the wrong one!

  If for instance you are iterating through an interval of dates, you might
  assume that the week always belongs to the same year as the given date,
  which unfortunately is B<WRONG> in some cases!

  In many years, the 31st of December for instance belongs to week number
  one of the B<FOLLOWING> year. Assuming that the year is the same as your
  date (31st of December, in this example), sends you back to the first week
  of the B<CURRENT> year - the Monday of which, by the way, in case of bad
  luck, might actually lie in the year B<BEFORE> the current year!

  This actually happens in 2002, for example.

  So you always need to provide the correct corresponding year number
  by other means, keeping track of it yourself.

  In case you do not understand this, never mind, but then simply
  B<DO NOT USE> this function in scalar context!

  =item *

  C<($year,$month,$day) = Monday_of_Week($week,$year);>

  This function returns the date of the first day of the given week, i.e.,
  the Monday.

  "C<$year>" must be greater than or equal to "C<1>", and "C<$week>" must
  lie in the range "C<1>" to "C<Weeks_in_Year($year)>".

  Note that you can write
  "C<($year,$month,$day) = Monday_of_Week(Week_of_Year($year,$month,$day));>"
  in order to calculate the date of the Monday of the same week as the
  given date.

  If you want to calculate any other day of week in the same week as a
  given date, use

    @date = Add_Delta_Days(Monday_of_Week(Week_of_Year(@date)),$offset);

  where C<$offset = 1> for Tuesday, C<2> for Wednesday etc.

  =item *

  C<if (($year,$month,$day) = Nth_Weekday_of_Month_Year($year,$month,$dow,$n))>

  This function calculates the date of the "C<$n>"th day of week "C<$dow>"
  in the given month "C<$month>" and year "C<$year>"; such as, for example,
  the 3rd Thursday of a given month and year.

  This can be used to send a notification mail to the members of a group
  which meets regularly on every 3rd Thursday of a month, for instance.

  (See the section "RECIPES" near the end of this document for a code
  snippet to actually do so.)

  "C<$year>" must be greater than or equal to "C<1>", "C<$month>" must lie
  in the range "C<1>" to "C<12>", "C<$dow>" must lie in the range "C<1>"
  to "C<7>" and "C<$n>" must lie in the range "C<1>" to "C<5>", or a fatal
  error (with appropriate error message) occurs.

  The function returns an empty list when the 5th of a given day of week
  does not exist in the given month and year.

  =item *

  C<($year,$week,$dow) = Standard_to_Business($year,$month,$day);>

  This function converts a given date from standard notation (year,
  month, day (of month)) to business notation (year, week, day of week).

  =item *

  C<($year,$month,$day) = Business_to_Standard($year,$week,$dow);>

  This function converts a given date from business notation (year,
  week, day of week) to standard notation (year, month, day (of month)).

  =item *

  C<$Dd = Delta_Days($year1,$month1,$day1, $year2,$month2,$day2);>

  This function returns the difference in days between the two given
  dates.

  The result is positive if the two dates are in chronological order,
  i.e., if date #1 comes chronologically B<BEFORE> date #2, and negative
  if the order of the two dates is reversed.

  The result is zero if the two dates are identical.

  =item *

  C<($Dd,$Dh,$Dm,$Ds) = Delta_DHMS($year1,$month1,$day1, $hour1,$min1,$sec1, $year2,$month2,$day2, $hour2,$min2,$sec2);>

  This function returns the difference in days, hours, minutes and seconds
  between the two given dates with times.

  All four return values will be positive if the two dates are in chronological
  order, i.e., if date #1 comes chronologically B<BEFORE> date #2, and negative
  (in all four return values!) if the order of the two dates is reversed.

  This is so that the two functions "C<Delta_DHMS()>" and "C<Add_Delta_DHMS()>"
  (description see further below) are complementary, i.e., mutually inverse:

    Add_Delta_DHMS(@date1,@time1, Delta_DHMS(@date1,@time1, @date2,@time2))

  yields "C<(@date2,@time2)>" again, whereas

    Add_Delta_DHMS(@date2,@time2,
        map(-$_, Delta_DHMS(@date1,@time1, @date2,@time2)))

  yields "C<(@date1,@time1)>", and

    Delta_DHMS(@date1,@time1, Add_Delta_DHMS(@date1,@time1, @delta))

  yields "C<@delta>" again.

  The result is zero (in all four return values) if the two dates and times
  are identical.

  =item *

  C<($Dy,$Dm,$Dd) = Delta_YMD($year1,$month1,$day1, $year2,$month2,$day2);>

  This function returns the vector

      ( $year2 - $year1, $month2 - $month1, $day2 - $day1 )

  This is called the "one-by-one" semantics.

  Adding the result of this function to the first date always yields the
  second date again, and adding the negative result (where the signs of
  all elements of the result vector have been flipped) to the second
  date gives the first date. See also the description of the function
  "Add_Delta_YMD()" further below.

  Example:

    (6,2,-30) == Delta_YMD(1996,1,31, 2002,3,1]);

    [1996,1,31] + ( 6, 2,-30) = [2002,3, 1]
    [2002,3, 1] + (-6,-2, 30) = [1996,1,31]

  An error occurs if any of the two given dates is invalid.

  =item *

  C<($D_y,$D_m,$D_d, $Dh,$Dm,$Ds) = Delta_YMDHMS($year1,$month1,$day1, $hour1,$min1,$sec1, $year2,$month2,$day2, $hour2,$min2,$sec2);>

  This function is based on the function "Delta_YMD()" above but additionally
  calculates the time difference. When a carry over from the time difference
  occurs, the value of "C<$D_d>" is adjusted accordingly, thus giving the
  correct total date/time difference.

  Arguments are expected to be in chronological order to yield a (usually)
  positive result.

  In any case, adding the result of this function to the first date/time value
  (C<$year1,$month1,$day1,> C<$hour1,$min1,$sec1>) always gives the second
  date/time value (C<$year2,$month2,$day2,> C<$hour2,$min2,$sec2>) again,
  and adding the negative result (with the signs of all elements of the result
  vector flipped) to the second date/time value gives the first date/time value.

  See the function "Add_Delta_YMDHMS()" further below for adding a date/time
  value and a date/time difference.

  An error occurs if any of the given two date/time values is invalid.

  =item *

  C<($Dy,$Dm,$Dd) = N_Delta_YMD($year1,$month1,$day1, $year2,$month2,$day2);>

  This function returns the difference between the two given dates in a
  more intuitive way (as far as possible - more on that see a bit further
  below) than the function "Delta_YMD()" described above.

  The "N" which precedes its name is meant to signify "new" or "normalized".

  This function is loosely based on recipe #17 b) (see the section "RECIPES"
  below near the end of this document).

  However, the code of recipe #17 b) actually does not treat positive and
  negative values symmetrically and consistently.

  This new routine does.

  The return values of this function are guaranteed to all have the same
  sign (or to be zero). This is why this function is called "normalized".

  Moreover, the results are guaranteed to be "minimal", in the sense that
  C<|$Dm| E<lt> 12> and C<|$Dd| E<lt> 31> (which is equivalent to C<$Dm>
  lying in the range C<[-11..+11]> and C<$Dd> lying in the range C<[-30..+30]>).

  When the results are applied (i.e., added) to the first given date in a
  left-to-right order, the second given date is guaranteed to be obtained,
  provided that intermediary results are truncated, as done by the function
  "Add_Delta_YM()" (see further below), i.e., that invalid intermediate dates
  such as e.g. [2009,2,31] will automatically be transformed into [2009,2,28]
  (and not "wrapped" into the next month, e.g. to [2009,3,3]).

  This is called the "left-to-right with truncation" semantics.

  Note that reversing the order of the given dates and reversing the sign of
  each of the result values will not always add up.

  Consider the dates [2008,2,29] and [2009,2,1]: their difference is (0,11,3)
  ([2008,2,29] plus 11 months is [2009,1,29], which plus 3 days is [2009,2,1]),
  but the difference between [2009,2,1] and [2008,2,29] is (0,-11,-1), and
  not (0,-11,-3) ([2009,2,1] minus 11 months is [2008,3,1], which minus one
  day is [2008,2,29]).

  Another example: The difference between [1996,2,29] and [1997,2,28] is (1,0,0)
  (observe the truncation of the invalid date [1997,2,29] to [1997,2,28] here!),
  whereas the difference between [1997,2,28] and [1996,2,29] is (0,-11,-28)
  ([1997,2,28] minus 11 months is [1996,3,28], which minus 28 days is not
  [1996,3,0] but of course [1996,2,29]).

  "Benign" examples such as for instance the difference between [1964,1,3]
  and [2009,9,10] are completely symmetrical: The difference in this example
  is (45,8,7), whereas the difference between [2009,9,10] and [1964,1,3] is
  (-45,-8,-7), as would normally be expected. In this example, the result
  is also the same as the one returned by "Delta_YMD()".

  All these counter-intuitive effects are due to the fact that months
  (and due to leap years, also years) do not correspond to a fixed number
  of days, so the semantics of "plus one month" or "plus one year" are in
  fact undefined.

  The present function is an attempt to provide a definition which is
  intuitive most of the time, and at least consistent the rest of the
  time.

  Other definitions are of course possible, but most often lead to
  contradictions (e.g., the results and the given first date do not
  add up to the second given date).

  See the file "datecalc.pl" in the "examples" subdirectory of this
  distribution for a way to play around with this function, or go to
  http://www.engelschall.com/u/sb/datecalc/ for the online version.

  An error occurs if any of the two given dates is invalid, or if any
  intermediate result leads to an invalid date (this does not apply
  to truncation, however, as explained above).

  =item *

  C<($D_y,$D_m,$D_d, $Dhh,$Dmm,$Dss) = N_Delta_YMDHMS($year1,$month1,$day1, $hour1,$min1,$sec1, $year2,$month2,$day2, $hour2,$min2,$sec2);>

  This function essentially does the same as the function "N_Delta_YMD()"
  described immediately above, except that also the difference in hours,
  minutes and seconds is taken into account.

  This function is loosely based on recipe #17 a) (see the section "RECIPES"
  below near the end of this document).

  However, the code of recipe #17 a) actually does not treat positive and
  negative values symmetrically and consistently.

  This new routine does.

  The return values of this function (including the time differences)
  are guaranteed to all have the same sign (or to be zero). This is the
  reason for the "N" that precedes the name of this function, which
  is intended to mean "normalized" (or "new").

  Moreover, the results are guaranteed to be "minimal", in the sense that
  C<|$D_m| E<lt> 12>, C<|$D_d| E<lt> 31>, C<|$Dhh| E<lt> 24>, C<|$Dmm| E<lt> 60>
  and C<|$Dss| E<lt> 60> (which is equivalent to C<$D_m> lying in the range
  C<[-11..+11]>, C<$D_d> lying in the range C<[-30..+30]>, C<$Dhh> lying in the
  range C<[-23..+23]>, and C<$Dmm> and C<$Dss> both lying in the range C<[-59..+59]>).

  =item *

  C<($Dd,$Dh,$Dm,$Ds) = Normalize_DHMS($Dd,$Dh,$Dm,$Ds);>

  This function takes four arbitrary values for days, hours, minutes
  and seconds (which may have different signs) and renormalizes them
  so that the values for hours, minutes and seconds will lie in the
  ranges C<[-23..23]>, C<[-59..59]> and C<[-59..59]>, respectively,
  and so that all four values have the same sign (or are zero).

  The given values are left untouched, i.e., unchanged.

  =item *

  C<($year,$month,$day) = Add_Delta_Days($year,$month,$day, $Dd);>

  This function has two principal uses:

  First, it can be used to calculate a new date, given an initial date and
  an offset (which may be positive or negative) in days, in order to answer
  questions like "today plus 90 days -- which date gives that?".

  (In order to add a weeks offset, simply multiply the weeks offset with
  "C<7>" and use that as your days offset.)

  Second, it can be used to convert the canonical representation of a date,
  i.e., the number of that day (where counting starts at the 1st of January
  in S<1 A.D.>), back into a date given as year, month and day.

  Because counting starts at "C<1>", you will actually have to subtract "C<1>"
  from the canonical date in order to get back the original date:

    $canonical = Date_to_Days($year,$month,$day);

    ($year,$month,$day) = Add_Delta_Days(1,1,1, $canonical - 1);

  Moreover, this function is the inverse of the function "C<Delta_Days()>":

    Add_Delta_Days(@date1, Delta_Days(@date1, @date2))

  yields "C<@date2>" again, whereas

    Add_Delta_Days(@date2, -Delta_Days(@date1, @date2))

  yields "C<@date1>", and

    Delta_Days(@date1, Add_Delta_Days(@date1, $delta))

  yields "C<$delta>" again.

  =item *

  C<($year,$month,$day, $hour,$min,$sec) = Add_Delta_DHMS($year,$month,$day, $hour,$min,$sec, $Dd,$Dh,$Dm,$Ds);>

  This function serves to add a days, hours, minutes and seconds offset to a
  given date and time, in order to answer questions like "today and now plus
  7 days but minus 5 hours and then plus 30 minutes, what date and time gives
  that?":

    ($y,$m,$d,$H,$M,$S) = Add_Delta_DHMS(Today_and_Now(), +7,-5,+30,0);

  =item *

  C<($year,$month,$day) = Add_Delta_YM($year,$month,$day, $Dy,$Dm);>

  This function can be used to add a year and/or month offset to a given
  date.

  In contrast to the function described immediately below
  ("C<Add_Delta_YMD()>"), this function does no "wrapping" into
  the next month if the day happens to lie outside the valid range
  for the resulting year and month (after adding the year and month
  offsets). Instead, it simply truncates the day to the last possible
  day of the resulting month.

  Examples:

  Adding an offset of 0 years, 1 month to the date [1999,1,31] would result
  in the (invalid) date [1999,2,31]. The function replaces this result by
  the (valid) date [1999,2,28].

  Adding an offset of 1 year, 1 month to the same date [1999,1,31] as above
  would result in the (still invalid) date [2000,2,31]. The function replaces
  this result by the valid date [2000,2,29] (because 2000 is a leap year).

  Note that the year and month offsets can be negative, and that they can
  have different signs.

  If you want to additionally add a days offset, use the function
  "C<Add_Delta_Days()>" before or after calling "C<Add_Delta_YM()>":

    @date2 = Add_Delta_Days( Add_Delta_YM(@date1, $Dy,$Dm), $Dd );
    @date2 = Add_Delta_YM( Add_Delta_Days(@date1, $Dd), $Dy,$Dm );

  Note that your result may depend on the order in which you call
  these two functions!

  Consider the date [1999,2,28] and the offsets 0 years, 1 month
  and 1 day:

  [1999,2,28] plus one month is [1999,3,28], plus one day is
  [1999,3,29]. [1999,2,28] plus one day is [1999,3,1], plus
  one month is [1999,4,1].

  (Which is also the reason why the "C<Add_Delta_YM()>" function
  does not allow to add a days offset, because this would actually
  require TWO functions: One for adding the days offset BEFORE and
  one for adding it AFTER applying the year/month offsets.)

  An error occurs if the initial date is not valid.

  Note that "C<Add_Delta_YM( Add_Delta_YM(@date, $Dy,$Dm), -$Dy,-$Dm );>"
  will not, in general, return the original date "C<@date>" (consider
  the examples given above!).

  =item *

  C<($year,$month,$day) = Add_Delta_YMD($year,$month,$day, $Dy,$Dm,$Dd);>

  This function serves to add a years, months and days offset to a given date.

  (In order to add a weeks offset, simply multiply the weeks offset with "C<7>"
  and add this number to your days offset.)

  Note that the three offsets for years, months and days are applied
  independently from each other. This also allows them to have
  different signs.

  The years and months offsets are applied first, and the days offset
  is applied last.

  If the resulting date happens to fall on a day after the end of the
  resulting month, like the 32nd of April or the 30th of February, then
  the date is simply counted forward into the next month (possibly also
  into the next year) by the number of excessive days (e.g., the 32nd of
  April will become the 2nd of May).

  B<BEWARE> that this behaviour differs from that of previous versions
  of this module! In previous versions, the day was simply truncated to
  the maximum number of days in the resulting month.

  If you want the previous behaviour, use the new function "C<Add_Delta_YM()>"
  (described immediately above) plus the function "C<Add_Delta_Days()>"
  instead.

  B<BEWARE> also that because a year and a month offset is not equivalent
  to a fixed number of days, the transformation performed by this function
  is B<NOT ALWAYS REVERSIBLE>!

  This is in contrast to the functions "C<Add_Delta_Days()>" and
  "C<Add_Delta_DHMS()>", which are fully and truly reversible (with
  the help of the functions "C<Delta_Days()>" and "C<Delta_DHMS()>",
  for instance).

  Note that for this same reason,

    @date = Add_Delta_YMD(
            Add_Delta_YMD(@date, $Dy,$Dm,$Dd), -$Dy,-$Dm,-$Dd);

  will in general B<NOT> return the initial date "C<@date>", even
  though

    @date2 = Add_Delta_YMD( @date1, Delta_YMD(@date1, @date2) );

  will always return the second date "C<@date2>", and

    @date1 = Add_Delta_YMD( @date2, map(-$_, Delta_YMD(@date1, @date2)) );

  which is the same as

    @date1 = Add_Delta_YMD( @date2, Delta_YMD(@date2, @date1) );

  will always return the first date "C<@date1>".

  Examples:

    [1996,1,31] + ( 6, 1,-2) = [2002,3,1]
    [2002,3, 1] + (-6,-1, 2) = [1996,2,3] # EXPECTED: [1996,1,31]

    (6,2,-30) == Delta_YMD(1996,1,31, 2002,3,1);

    [1996,1,31] + ( 6, 2,-30) = [2002,3, 1]
    [2002,3, 1] + (-6,-2, 30) = [1996,1,31] # OK

    (6,1,-2) == Delta_YMD(1996,2,3, 2002,3,1);

    [1996,2,3] + ( 6, 1,-2) = [2002,3,1]
    [2002,3,1] + (-6,-1, 2) = [1996,2,3] # OK

  Note that this is B<NOT> a program bug but B<NECESSARILY> so,
  because of the variable lengths of years and months, and hence
  because of the ambiguity of the difference between two dates
  in terms of years, months and days, i.e., the fact that the
  difference between two dates can be expressed in more than
  one way:

    [1996,1,31] + (6,1, -2) = [2002,3,1]
    [1996,1,31] + (6,2,-30) = [2002,3,1]

  =item *

  C<($year,$month,$day, $hour,$min,$sec) = Add_Delta_YMDHMS($year,$month,$day, $hour,$min,$sec, $D_y,$D_m,$D_d, $Dh,$Dm,$Ds);>

  Same as the function above, except that a time offset may be given in
  addition to the year, month and day offset.

  =item *

  C<($year,$month,$day) = Add_N_Delta_YMD($year,$month,$day, $Dy,$Dm,$Dd);>

  This function is actually a shortcut for applying the function "Add_Delta_YM()"
  first, followed by the function "Add_Delta_Days()", i.e., this function does
  exactly the same as

   ($year,$month,$day) = Add_Delta_Days( Add_Delta_YM($year,$month,$day,$Dy,$Dm), $Dd );

  Beware that, if necessary, the function "Add_Delta_YM()" truncates the
  resulting day of the month to the largest allowable value for that month,
  i.e., the (invalid) result [2009,2,31] is automatically transformed into
  [2009,2,28].

  For more details on this truncation, see the description of the function
  "Add_Delta_YM()" further above.

  This function is meant to be complementary with the function "N_Delta_YMD()"
  described further above.

  This means that it is guaranteed that the result returned by

    Add_N_Delta_YMD( @date1, N_Delta_YMD(@date1, @date2) );

  is always identical with the given date "C<@date2>".

  Note however that unlike with function "Add_Delta_YMD()",
  the reverse is not true here, i.e.,

    ($Dy,$Dm,$Dd) = N_Delta_YMD(@date1,@date2);
    @date = Add_N_Delta_YMD(@date2, -$Dy,-$Dm,-$Dd);

  will B<NOT> always return the initial date "C<@date1>".

  Example:

    (0,11,3) == N_Delta_YMD(2008,2,29, 2009,2,1);

    [2008,2,29] + (0, 11, 3) = [2009,2, 1]
    [2009,2, 1] + (0,-11,-3) = [2008,2,27] # EXPECTED: [2008,2,29]

  =item *

  C<($year,$month,$day, $hour,$min,$sec) = Add_N_Delta_YMDHMS($year,$month,$day, $hour,$min,$sec, $D_y,$D_m,$D_d, $Dhh,$Dmm,$Dss);>

  This function essentially does the same as the function "Add_N_Delta_YMD()"
  described immediately above, except that also the difference in hours,
  minutes and seconds is taken into account.

  =item *

  C<($year,$month,$day, $hour,$min,$sec, $doy,$dow,$dst) = System_Clock([$gmt]);>

  If your operating system supports the corresponding system calls
  ("C<time()>" and "C<localtime()>" or "C<gmtime()>"), this function
  will return the information provided by your system clock, i.e.,
  the current date and time, the number of the day of year, the number
  of the day of week and a flag signaling whether daylight savings time
  is currently in effect or not.

  The ranges of values returned (and their meanings) are as follows:

          $year   :   1970..2038 (or more)  [Unix etc.]
          $year   :   1904..2040            [MacOS Classic]

          $month  :   1..12
          $day    :   1..31
          $hour   :   0..23
          $min    :   0..59
          $sec    :   0..59    (0..61 on some systems)
          $doy    :   1..366
          $dow    :   1..7
          $dst    :  -1..1

  "C<$doy>" is the day of year, sometimes also referred to as the
  "julian date", which starts at "C<1>" and goes up to the number
  of days in that year.

  The day of week ("C<$dow>") will be "C<1>" for Monday, "C<2>" for
  Tuesday and so on until "C<7>" for Sunday.

  The daylight savings time flag ("C<$dst>") will be "C<-1>" if this
  information is not available on your system, "C<0>" for no daylight
  savings time (i.e., winter time) and "C<1>" when daylight savings
  time is in effect.

  If your operating system does not provide the necessary system calls,
  calling this function will result in a fatal "not available on this
  system" error message.

  If you want to handle this exception yourself, use "C<eval>" as follows:

    eval { ($year,$month,$day, $hour,$min,$sec, $doy,$dow,$dst) =
      System_Clock(); };

    if ($@)
    {
        
        
    }

  Note that curlies ("{" and "}") are used here to delimit the statement to
  be "eval"ed (which is the way to catch exceptions in Perl), and not quotes
  (which is a way to evaluate Perl expressions at runtime).

  If the optional (boolean) input parameter "C<$gmt>" is given, a "true"
  value ("C<1>") will cause "C<gmtime()>" to be used instead of "C<localtime()>",
  internally, thus returning Greenwich Mean Time (GMT, or UTC) instead of
  local time.

  =item *

  C<($year,$month,$day) = Today([$gmt]);>

  This function returns a subset of the values returned by the function
  "C<System_Clock()>" (see above for details), namely the current year,
  month and day.

  A fatal "not available on this system" error message will appear if the
  corresponding system calls are not supported by your current operating
  system.

  If the optional (boolean) input parameter "C<$gmt>" is given, a "true"
  value ("C<1>") will cause "C<gmtime()>" to be used instead of "C<localtime()>",
  internally, thus returning Greenwich Mean Time (GMT, or UTC) instead of
  local time.

  =item *

  C<($hour,$min,$sec) = Now([$gmt]);>

  This function returns a subset of the values returned by the function
  "C<System_Clock()>" (see above for details), namely the current time
  (hours, minutes and full seconds).

  A fatal "not available on this system" error message will appear if the
  corresponding system calls are not supported by your current operating
  system.

  If the optional (boolean) input parameter "C<$gmt>" is given, a "true"
  value ("C<1>") will cause "C<gmtime()>" to be used instead of "C<localtime()>",
  internally, thus returning Greenwich Mean Time (GMT, or UTC) instead of
  local time.

  =item *

  C<($year,$month,$day, $hour,$min,$sec) = Today_and_Now([$gmt]);>

  This function returns a subset of the values returned by the function
  "C<System_Clock()>" (see above for details), namely the current date
  (year, month, day) and time (hours, minutes and full seconds).

  A fatal "not available on this system" error message will appear if the
  corresponding system calls are not supported by your current operating
  system.

  If the optional (boolean) input parameter "C<$gmt>" is given, a "true"
  value ("C<1>") will cause "C<gmtime()>" to be used instead of "C<localtime()>",
  internally, thus returning Greenwich Mean Time (GMT, or UTC) instead of
  local time.

  =item *

  C<$year = This_Year([$gmt]);>

  This function returns the current year, according to local time.

  A fatal "not available on this system" error message will appear if the
  corresponding system calls are not supported by your current operating
  system.

  If the optional (boolean) input parameter "C<$gmt>" is given, a "true"
  value ("C<1>") will cause "C<gmtime()>" to be used instead of "C<localtime()>",
  internally, thus returning Greenwich Mean Time (GMT, or UTC) instead of
  local time. However, this will only make a difference within a few hours
  around New Year (unless you are on a Pacific island, where this can
  be almost 24 hours).

  =item *

  C<($year,$month,$day, $hour,$min,$sec, $doy,$dow,$dst) = Gmtime([time]);>

  This is Date::Calc's equivalent of Perl's built-in "gmtime()" function.
  See also L<perlfunc(1)/gmtime>.

  With the optional argument "time" (i.e., seconds since the epoch),
  this function will return the corresponding values for that particular
  time (instead of the current time when this parameter is omitted).

  The ranges of values returned (and their meanings) are as follows:

          $year   :   1970..2038 (or more)  [Unix etc.]
          $year   :   1904..2040            [MacOS Classic]

          $month  :   1..12
          $day    :   1..31
          $hour   :   0..23
          $min    :   0..59
          $sec    :   0..59
          $doy    :   1..366
          $dow    :   1..7
          $dst    :  -1..1

  "C<$doy>" is the day of year, sometimes also referred to as the
  "julian date", which starts at "C<1>" and goes up to the number
  of days in that year.

  The day of week ("C<$dow>") will be "C<1>" for Monday, "C<2>" for
  Tuesday and so on until "C<7>" for Sunday.

  The daylight savings time flag ("C<$dst>") will be "C<-1>" if this
  information is not available on your system, "C<0>" for no daylight
  savings time (i.e., winter time) and "C<1>" when daylight savings
  time is in effect.

  A fatal "time out of range" error will occur if the given time value
  is out of range C<[0..(~0E<gt>E<gt>1)]>.

  If the time value is omitted, the "time()" function is called instead,
  internally.

  =item *

  C<($year,$month,$day, $hour,$min,$sec, $doy,$dow,$dst) = Localtime([time]);>

  This is Date::Calc's equivalent of Perl's built-in "localtime()" function.
  See also L<perlfunc(1)/localtime>.

  The ranges of values returned (and their meanings) are as follows:

          $year   :   1970..2038 (or more)  [Unix etc.]
          $year   :   1904..2040            [MacOS Classic]

          $month  :   1..12
          $day    :   1..31
          $hour   :   0..23
          $min    :   0..59
          $sec    :   0..59
          $doy    :   1..366
          $dow    :   1..7
          $dst    :  -1..1

  "C<$doy>" is the day of year, sometimes also referred to as the
  "julian date", which starts at "C<1>" and goes up to the number
  of days in that year.

  The day of week ("C<$dow>") will be "C<1>" for Monday, "C<2>" for
  Tuesday and so on until "C<7>" for Sunday.

  The daylight savings time flag ("C<$dst>") will be "C<-1>" if this
  information is not available on your system, "C<0>" for no daylight
  savings time (i.e., winter time) and "C<1>" when daylight savings
  time is in effect.

  A fatal "time out of range" error will occur if the given time value is
  out of range C<[0..(~0E<gt>E<gt>1)]>.

  If the time value is omitted, the "time()" function is called instead,
  internally.

  =item *

  C<$time = Mktime($year,$month,$day, $hour,$min,$sec);>

  This function converts a date into a time value, i.e., into the number
  of seconds since whatever moment in time your system considers to be
  the "epoch". On Unix and most other systems this is the number of seconds
  since January 1st 1970 at midnight (GMT). On MacOS Classic this is the
  number of seconds since January 1st 1904 at midnight (local time).

  The function is similar to the "POSIX::mktime()" function (see L<POSIX(1)/mktime>
  for more details), but in contrast to the latter, it expects dates in the
  usual ranges used throughout this module: The year 2001 stays year 2001,
  and months are numbered from 1 to 12.

  A fatal "date out of range" error will occur if the given date cannot
  be expressed in terms of seconds since the epoch (this happens for
  instance when the date lies before the epoch, or if it is later than
  S<19-Jan-2038 03:14:07 GMT> on S<32 bit> Unix systems, or later than
  S<06-Feb-2040 06:28:15> (local time) on a Macintosh with MacOS Classic).

  Just like the "POSIX::mktime()" function, this function uses the
  "mktime()" system call, internally.

  This means that the given date and time is considered to be in local time,
  and that the value returned by this function will depend on your machine's
  local settings such as the time zone, whether daylight savings time is
  (or was, at the time) in effect, and the system clock itself.

  B<BEWARE> that "mktime()" does not always return the same time value
  as fed into "localtime()", when you feed the output of "localtime()"
  back into "mktime()", on some systems!

  I.e., "C<Mktime((Localtime($time))[0..5])>" will not always return
  the same value as given in "C<$time>"!

  =item *

  C<($D_y,$D_m,$D_d, $Dh,$Dm,$Ds, $dst) = Timezone([time]);>

  This function returns the difference between "C<localtime(time)>" and
  "C<gmtime(time)>", which is the timezone offset in effect for the current
  location and the given "C<time>".

  This offset is positive if you are located to the east of Greenwich,
  and is usually negative (except during daylight savings time, in some
  locations) if you are located to the west of Greenwich.

  Note that this offset is influenced by all of the relevant system
  settings and parameters on your machine; such as locales, environment
  variables (e.g. "C<TZ>") and the system clock itself. See the
  relevant documentation on your system for more details.

  If the "C<time>" is omitted, the "C<time()>" function will
  be called automatically, internally (similar to the built-in
  functions "C<localtime()>" and "C<gmtime()>" in Perl).

  A fatal "time out of range" error will occur if the given time value
  is out of range C<[0..(~0E<gt>E<gt>1)]>.

  The last item of the returned list is a flag which indicates whether
  daylight savings time is currently in effect. This flag is negative
  (-1) if this information is not available on your system. It is zero
  (0) when daylight savings time is off, and positive (+1) when daylight
  savings time is on.

  Thus you can check very quickly whether daylight savings time is
  currently in effect by evaluating this function in scalar context
  (in scalar context, Perl returns the last item of a list):

    if (scalar Timezone > 0) { # yes, daylight savings time

  However, a slightly more efficient way would be this:

    if (scalar System_Clock > 0) { # yes, daylight savings time

  =item *

  C<$time = Date_to_Time($year,$month,$day, $hour,$min,$sec);>

  This function is a replacement for the BSD function "timegm()"
  (which is not available on all Unix systems), which converts
  a given date and time into a time value, i.e., into the number
  of seconds since whatever moment in time your system considers to be
  the "epoch". On Unix and most other systems this is the number of seconds
  since January 1st 1970 at midnight (GMT). On MacOS Classic this is the
  number of seconds since January 1st 1904 at midnight (local time).

  Under Unix, the date and time are considered to be in UTC
  ("Universal Time Coordinated", and so is the resulting time value.

  UTC is almost the same as GMT (or "Greenwich Mean Time"), except
  that UTC has leap seconds (in order to account for small variations
  in the rotation of the earth, for instance), whereas GMT does not.

  Under MacOS Classic, however, both input and output are
  considered to be in local time.

  The ranges of year and month follow the same rules as throughout
  the rest of this module (and not the contorted rules of its Unix
  equivalent), i.e., the year "2001" stays "2001" and the month
  ranges from 1 to 12.

  A fatal "date out of range" error will occur if the given date cannot
  be expressed in terms of seconds since the epoch (this happens for
  instance when the date lies before the epoch, or if it is later than
  S<19-Jan-2038 03:14:07 GMT> on S<32 bit> Unix systems, or later than
  S<06-Feb-2040 06:28:15> (local time) on a Macintosh with MacOS Classic).

  This function should be very fast, because it is implemented in
  a very straightforward manner and doesn't use any internal system
  calls.

  Moreover, the functions "Date_to_Time()" and "Time_to_Date()"
  are guaranteed to be complementary, i.e., that
  "C<Date_to_Time(Time_to_Date($time))>" and
  "C<Time_to_Date(Date_to_Time($year,$month,$day, $hour,$min,$sec))>"
  will always return the initial values.

  =item *

  C<($year,$month,$day, $hour,$min,$sec) = Time_to_Date([time]);>

  This function is an alternative to the POSIX "gmtime()" function
  (and its built-in Perl equivalent), which converts a given time
  value into the corresponding date and time. The given time value
  must be the number of seconds since whatever moment in time your
  system considers to be the "epoch". On Unix and most other systems
  this is the number of seconds since January 1st 1970 at midnight
  (GMT). On MacOS Classic this is the number of seconds since
  January 1st 1904 at midnight (local time).

  Under Unix, the given time value is considered to be in UTC
  ("Universal Time Coordinated", and so is the resulting date
  and time.

  UTC is almost the same as GMT (or "Greenwich Mean Time"), except
  that UTC has leap seconds (in order to account for small variations
  in the rotation of the earth, for instance), whereas GMT does not.

  Under MacOS Classic, however, both input and output
  are considered to be in local time.

  If the input value "C<time>" is omitted, the "C<time()>" function
  will be called automatically, internally (similar to the built-in
  functions "C<localtime()>" and "C<gmtime()>" in Perl).

  A fatal "time out of range" error will occur if the given time
  value is negative.

  This function should be very fast, because it is implemented in
  a very straightforward manner and doesn't use any internal system
  calls (except for "time()", if the input value is omitted).

  Moreover, the functions "Date_to_Time()" and "Time_to_Date()"
  are guaranteed to be complementary, i.e., that
  "C<Date_to_Time(Time_to_Date($time))>" and
  "C<Time_to_Date(Date_to_Time($year,$month,$day, $hour,$min,$sec))>"
  will always return the initial values.

  =item *

  C<($year,$month,$day) = Easter_Sunday($year);>

  This function calculates the date of Easter Sunday for all years in the
  range from 1583 to 2299 (all other year numbers will result in a fatal
  "year out of range" error message) using the method known as the "Gaussian
  Rule".

  Some related christian feast days which depend on the date of Easter Sunday:

    Carnival Monday / Rosenmontag / Veille du Mardi Gras   =  -48 days
    Mardi Gras / Karnevalsdienstag / Mardi Gras            =  -47 days
    Ash Wednesday / Aschermittwoch / Mercredi des Cendres  =  -46 days
    Palm Sunday / Palmsonntag / Dimanche des Rameaux       =   -7 days
    Easter Friday / Karfreitag / Vendredi Saint            =   -2 days
    Easter Saturday / Ostersamstag / Samedi de Paques      =   -1 day
    Easter Monday / Ostermontag / Lundi de Paques          =   +1 day
    Ascension of Christ / Christi Himmelfahrt / Ascension  =  +39 days
    Whitsunday / Pfingstsonntag / Dimanche de Pentecote    =  +49 days
    Whitmonday / Pfingstmontag / Lundi de Pentecote        =  +50 days
    Feast of Corpus Christi / Fronleichnam / Fete-Dieu     =  +60 days

  Use the offsets shown above to calculate the date of the corresponding
  feast day as follows:

    ($year,$month,$day) = Add_Delta_Days(Easter_Sunday($year), $offset));

  =item *

  C<if ($month = Decode_Month($string[,$lang]))>

  This function takes a string as its argument, which should contain the
  name of a month in the given or currently selected language (see further below
  for details about the multi-language support of this package), or any uniquely
  identifying abbreviation of a month's name (i.e., the first few letters),
  and returns the corresponding number (1..12) upon a successful match, or
  "C<0>" otherwise (therefore, the return value can also be used as the
  conditional expression in an "if" statement).

  Note that the input string may not contain any other characters which do not
  pertain to the month's name, especially no leading or trailing whitespace.

  Note also that matching is performed in a case-insensitive manner (this may
  depend on the "locale" setting on your current system, though!)

  With "1" ("English") as the given language, the following examples will
  all return the value "C<9>":

    $month = Decode_Month("s",1);
    $month = Decode_Month("Sep",1);
    $month = Decode_Month("septemb",1);
    $month = Decode_Month("September",1);

  =item *

  C<if ($dow = Decode_Day_of_Week($string[,$lang]))>

  This function takes a string as its argument, which should contain the
  name of a day of week in the given or currently selected language (see further
  below for details about the multi-language support of this package), or any
  uniquely identifying abbreviation of the name of a day of week (i.e., the
  first few letters), and returns the corresponding number (1..7) upon a
  successful match, or "C<0>" otherwise (therefore, the return value can
  also be used as the conditional expression in an "if" statement).

  Note that the input string may not contain any other characters which
  do not pertain to the name of the day of week, especially no leading
  or trailing whitespace.

  Note also that matching is performed in a case-insensitive manner (this may
  depend on the "locale" setting on your current system, though!)

  With "1" ("English") as the given language, the following examples will
  all return the value "C<3>":

    $dow = Decode_Day_of_Week("w",1);
    $dow = Decode_Day_of_Week("Wed",1);
    $dow = Decode_Day_of_Week("wednes",1);
    $dow = Decode_Day_of_Week("Wednesday",1);

  =item *

  C<if ($lang = Decode_Language($string))>

  This function takes a string as its argument, which should contain the
  name of one of the languages supported by this package (B<IN THIS VERY
  LANGUAGE ITSELF>), or any uniquely identifying abbreviation of the name
  of a language (i.e., the first few letters), and returns its corresponding
  internal number (1..14 in the original distribution) upon a successful match,
  or "C<0>" otherwise (therefore, the return value can also be used as the
  conditional expression in an "if" statement).

  Note that the input string may not contain any other characters which do
  not pertain to the name of a language, especially no leading or trailing
  whitespace.

  Note also that matching is performed in a case-insensitive manner (this may
  depend on the "locale" setting on your current system, though!)

  The original distribution supports the following fourteen languages:

              English                    ==>    1    (default)
              Français    (French)       ==>    2
              Deutsch     (German)       ==>    3
              Español     (Spanish)      ==>    4
              Português   (Portuguese)   ==>    5
              Nederlands  (Dutch)        ==>    6
              Italiano    (Italian)      ==>    7
              Norsk       (Norwegian)    ==>    8
              Svenska     (Swedish)      ==>    9
              Dansk       (Danish)       ==>   10
              suomi       (Finnish)      ==>   11
              Magyar      (Hungarian)    ==>   12
              polski      (Polish)       ==>   13
              Romaneste   (Romanian)     ==>   14

  See the section "How to install additional languages" in the file
  "INSTALL.txt" in this distribution for how to add more languages
  to this package.

  In the original distribution (no other languages installed),
  the following examples will all return the value "C<3>":

    $lang = Decode_Language("d");
    $lang = Decode_Language("de");
    $lang = Decode_Language("Deutsch");

  Note that you may not be able to enter the special international characters
  in some of the languages' names over the keyboard directly on some systems.

  This should never be a problem, though; just enter an abbreviation of the
  name of the language consisting of the first few letters up to the character
  before the first special international character.

  =item *

  C<if (($year,$month,$day) = Decode_Date_EU($string[,$lang]))>

  This function scans a given string and tries to parse any date
  which might be embedded in it.

  The function returns an empty list if it can't successfully
  extract a valid date from its input string, or else it returns
  the date found.

  The function accepts almost any format, as long as the date is
  given in the european order (hence its name) day-month-year.

  Thereby, zero or more B<NON-NUMERIC> characters may B<PRECEDE>
  the day and B<FOLLOW> the year.

  Moreover, zero or more B<NON-ALPHANUMERIC> characters are permitted
  B<BETWEEN> these three items (i.e., between day and month and between
  month and year).

  The month may be given either numerically (i.e., a number from "C<1>"
  to "C<12>"), or alphanumerically, i.e., as the name of the month in
  the given or currently selected language, or any uniquely identifying
  abbreviation thereof.

  (See further below for details about the multi-language support of this
  package!)

  If the year is given as one or two digits only (i.e., if the year is less
  than 100), it is mapped to a "window" of +/- 50 years around the current
  year, as described by the "Moving_Window()" function (see further below).

  If the day, month and year are all given numerically but B<WITHOUT> any
  delimiting characters between them, this string of digits will be mapped
  to the day, month and year as follows:

                  Length:        Mapping:
                    3              dmy
                    4              dmyy
                    5              dmmyy
                    6              ddmmyy
                    7              dmmyyyy
                    8              ddmmyyyy

  (Where "d" stands for "day", "m" stands for "month" and "y" stands for
  "year".)

  All other strings consisting purely of digits (without any intervening
  delimiters) are rejected, i.e., not recognized.

  Examples:

    "3.1.64"
    "3 1 64"
    "03.01.64"
    "03/01/64"
    "3. Jan 1964"
    "Birthday: 3. Jan '64 in Backnang/Germany"
    "03-Jan-64"
    "3.Jan1964"
    "3Jan64"
    "030164"
    "3ja64"
    "3164"

  Experiment! (See the corresponding example applications in the
  "examples" subdirectory of this distribution in order to do so.)

  =item *

  C<if (($year,$month,$day) = Decode_Date_US($string[,$lang]))>

  This function scans a given string and tries to parse any date
  which might be embedded in it.

  The function returns an empty list if it can't successfully
  extract a valid date from its input string, or else it returns
  the date found.

  The function accepts almost any format, as long as the date is
  given in the U.S. american order (hence its name) month-day-year.

  Thereby, zero or more B<NON-ALPHANUMERIC> characters may B<PRECEDE>
  and B<FOLLOW> the month (i.e., precede the month and separate it from
  the day which follows behind).

  Moreover, zero or more B<NON-NUMERIC> characters are permitted
  B<BETWEEN> the day and the year, as well as B<AFTER> the year.

  The month may be given either numerically (i.e., a number from "C<1>"
  to "C<12>"), or alphanumerically, i.e., as the name of the month in
  the given or currently selected language, or any uniquely identifying
  abbreviation thereof.

  (See further below for details about the multi-language support of this
  package!)

  If the year is given as one or two digits only (i.e., if the year is less
  than 100), it is mapped to a "window" of +/- 50 years around the current
  year, as described by the "Moving_Window()" function (see further below).

  If the month, day and year are all given numerically but B<WITHOUT> any
  delimiting characters between them, this string of digits will be mapped
  to the month, day and year as follows:

                  Length:        Mapping:
                    3              mdy
                    4              mdyy
                    5              mddyy
                    6              mmddyy
                    7              mddyyyy
                    8              mmddyyyy

  (Where "m" stands for "month", "d" stands for "day" and "y" stands for
  "year".)

  All other strings consisting purely of digits (without any intervening
  delimiters) are rejected, i.e., not recognized.

  If only the day and the year form a contiguous string of digits, they
  will be mapped as follows:

                  Length:        Mapping:
                    2              dy
                    3              dyy
                    4              ddyy
                    5              dyyyy
                    6              ddyyyy

  (Where "d" stands for "day" and "y" stands for "year".)

  Examples:

    "1 3 64"
    "01/03/64"
    "Jan 3 '64"
    "Jan 3 1964"
    "===> January 3rd 1964 (birthday)"
    "Jan31964"
    "Jan364"
    "ja364"
    "1364"

  Experiment! (See the corresponding example applications in the
  "examples" subdirectory of this distribution in order to do so.)

  =item *

  C<$year = Fixed_Window($yy);>

  This function applies a "fixed window" strategy to two-digit year
  numbers in order to convert them into four-digit year numbers.

  All other year numbers are passed through unchanged, except for
  negative year numbers, which cause the function to return zero
  ("C<0>") instead.

  Two-digit year numbers "C<yy>" below 70 are converted to "C<20yy>",
  whereas year numbers equal to or greater than 70 (but less than 100)
  are converted to "C<19yy>".

  In the original distribution of this package, the base century is
  set to "1900" and the base year to "70" (which is a standard on UNIX
  systems), but these constants (also called the "epoch") can actually
  be chosen at will (in the files "DateCalc.c" and "DateCalc.h") at
  compile time of this module.

  =item *

  C<$year = Moving_Window($yy);>

  This function applies a "moving window" strategy to two-digit year
  numbers in order to convert them into four-digit year numbers, provided
  the necessary system calls (system clock) are available. Otherwise the
  function falls back to the "fixed window" strategy described in the
  function above.

  All other year numbers are passed through unchanged, except for
  negative year numbers, which cause the function to return zero
  ("C<0>") instead.

  Two-digit year numbers are mapped according to a "window" of 50 years
  in both directions (past and future) around the current year.

  That is, two-digit year numbers are first mapped to the same century
  as the current year. If the resulting year is smaller than the current
  year minus 50, then one more century is added to the result. If the
  resulting year is equal to or greater than the current year plus 50,
  then a century is subtracted from the result.

  =item *

  C<$date = Compress($year,$month,$day);>

  WARNING: This function is legacy code, its use is deprecated!

  This function encodes a date in 16 bits, which is the value being returned.

  The encoding scheme is as follows:

              Bit number:    FEDCBA9 8765 43210
              Contents:      yyyyyyy mmmm ddddd

  (Where the "yyyyyyy" contain the number of the year, "mmmm" the number of
  the month and "ddddd" the number of the day.)

  The function returns "C<0>" if the given input values do not represent a
  valid date. Therefore, the return value of this function can also be used
  as the conditional expression in an "if" statement, in order to check
  whether the given input values constitute a valid date).

  Through this special encoding scheme, it is possible to B<COMPARE>
  compressed dates for equality and order (less than/greater than)
  B<WITHOUT> any previous B<DECODING>!

  Note however that contiguous dates do B<NOT> necessarily have contiguous
  compressed representations!

  I.e., incrementing the compressed representation of a date B<MAY OR MAY NOT>
  yield a valid new date!

  Note also that this function can only handle dates within one century.

  This century can be chosen at will (at compile time of this module)
  by defining a base century and year (also called the "epoch"). In the
  original distribution of this package, the base century is set to
  "1900" and the base year to "70" (which is standard on UNIX systems).

  This allows this function to handle dates from "1970" up to "2069".

  If the given year is equal to, say, "95", this package will automatically
  assume that you really meant "1995" instead. However, if you specify a year
  number which is B<SMALLER> than 70, like "64", for instance, this package
  will assume that you really meant "2064".

  You are not confined to two-digit (abbreviated) year numbers, though.

  The function also accepts "full-length" year numbers, provided that they
  lie in the supported range (i.e., from "1970" to "2069", in the original
  configuration of this package).

  Note that this function is maintained mainly for backward compatibility,
  and that its use is not recommended.

  =item *

  C<if (($century,$year,$month,$day) = Uncompress($date))>

  WARNING: This function is legacy code, its use is deprecated!

  This function decodes dates that were encoded previously using the function
  "C<Compress()>".

  It returns the century, year, month and day of the date encoded in "C<$date>"
  if "C<$date>" represents a valid date, or an empty list otherwise.

  The year returned in "C<$year>" is actually a two-digit year number
  (i.e., the year number taken modulo 100), and only the expression
  "C<$century + $year>" yields the "full-length" year number
  (for example, C<1900 + 95 = 1995>).

  Note that this function is maintained mainly for backward compatibility,
  and that its use is not recommended.

  =item *

  C<if (check_compressed($date))>

  WARNING: This function is legacy code, its use is deprecated!

  This function returns "true" ("C<1>") if the given input value
  constitutes a valid compressed date, and "false" ("C<0>") otherwise.

  Note that this function is maintained mainly for backward compatibility,
  and that its use is not recommended.

  =item *

  C<$string = Compressed_to_Text($date[,$lang]);>

  WARNING: This function is legacy code, its use is deprecated!

  This function returns a string of fixed length (always 9 characters long)
  containing a textual representation of the compressed date encoded in
  "C<$date>".

  This string has the form "dd-Mmm-yy", where "dd" is the two-digit number
  of the day, "Mmm" are the first three letters of the name of the month
  in the given or currently selected language (see further below for details
  about the multi-language support of this package), and "yy" is the two-digit
  year number (i.e., the year number taken modulo 100).

  If "C<$date>" does not represent a valid date, the string "??-???-??" is
  returned instead.

  Note that this function is maintained mainly for backward compatibility,
  and that its use is not recommended.

  =item *

  C<$string = Date_to_Text($year,$month,$day[,$lang]);>

  This function returns a string containing a textual representation of the
  given date of the form "www dd-Mmm-yyyy", where "www" are the first three
  letters of the name of the day of week in the given or currently selected
  language, or a special abbreviation, if special abbreviations have been
  defined for the given or currently selected language (see further below for
  details about the multi-language support of this package), "dd" is the day
  (one or two digits), "Mmm" are the first three letters of the name of the
  month in the given or currently selected language, and "yyyy" is the number
  of the year in full length.

  If the given input values do not constitute a valid date, a fatal "not a
  valid date" error occurs.

  (See the section "RECIPES" near the end of this document for a code snippet
  for how to print dates in any format you like.)

  =item *

  C<$string = Date_to_Text_Long($year,$month,$day[,$lang]);>

  This function returns a string containing a textual representation of the
  given date roughly of the form "Wwwwww, dd Mmmmmm yyyy", where "Wwwwww"
  is the name of the day of week in the given or currently selected language
  (see further below for details about the multi-language support of this package),
  "dd" is the day (one or two digits), "Mmmmmm" is the name of the month
  in the given or currently selected language, and "yyyy" is the number of
  the year in full length.

  The exact format of the output string depends on the given or currently
  selected language. In the original distribution of this package, these
  formats are defined as follows:

    1  English    :  "Wwwwww, Mmmmmm ddth yyyy"
    2  French     :  "Wwwwww dd mmmmmm yyyy"
    3  German     :  "Wwwwww, den dd. Mmmmmm yyyy"
    4  Spanish    :  "Wwwwww, dd de mmmmmm de yyyy"
    5  Portuguese :  "Wwwwww, dia dd de mmmmmm de yyyy"
    6  Dutch      :  "Wwwwww, dd mmmmmm yyyy"
    7  Italian    :  "Wwwwww, dd Mmmmmm yyyy"
    8  Norwegian  :  "wwwwww, dd. mmmmmm yyyy"
    9  Swedish    :  "wwwwww, dd mmmmmm yyyy"
   10  Danish     :  "wwwwww, dd. mmmmmm yyyy"
   11  Finnish    :  "wwwwww, dd. mmmmmmta yyyy"
   12  Hungarian  :  "dd. Mmmmmm yyyy., wwwwww"
   13  Polish     :  "Wwwwww, dd Mmmmmm yyyy"
   14  Romanian   :  "Wwwwww dd Mmmmmm yyyy"

  (You can change these formats in the file "DateCalc.c" before
  building this module in order to suit your personal preferences.)

  If the given input values do not constitute a valid date, a fatal
  "not a valid date" error occurs.

  In order to capitalize the day of week at the beginning of the string
  in Norwegian, use "C<ucfirst(Date_to_Text_Long($year,$month,$day,8));>".

  (See the section "RECIPES" near the end of this document for
  an example on how to print dates in any format you like.)

  =item *

  C<$string = English_Ordinal($number);>

  This function returns a string containing the (english) abbreviation
  of the ordinal number for the given (cardinal) number "C<$number>".

  I.e.,

      0  =>  '0th'    10  =>  '10th'    20  =>  '20th'
      1  =>  '1st'    11  =>  '11th'    21  =>  '21st'
      2  =>  '2nd'    12  =>  '12th'    22  =>  '22nd'
      3  =>  '3rd'    13  =>  '13th'    23  =>  '23rd'
      4  =>  '4th'    14  =>  '14th'    24  =>  '24th'
      5  =>  '5th'    15  =>  '15th'    25  =>  '25th'
      6  =>  '6th'    16  =>  '16th'    26  =>  '26th'
      7  =>  '7th'    17  =>  '17th'    27  =>  '27th'
      8  =>  '8th'    18  =>  '18th'    28  =>  '28th'
      9  =>  '9th'    19  =>  '19th'    29  =>  '29th'

  etc.

  =item *

  C<$string = Calendar($year,$month[,$orthodox[,$lang]]);>

  This function returns a calendar of the given month in the given year
  (somewhat similar to the UNIX "C<cal>" command), in the given or currently
  selected language (see further below for details about the multi-language
  support of this package).

  Example:

    print Calendar(1998,5);

  This will print:

             May 1998
    Mon Tue Wed Thu Fri Sat Sun
                      1   2   3
      4   5   6   7   8   9  10
     11  12  13  14  15  16  17
     18  19  20  21  22  23  24
     25  26  27  28  29  30  31

  If the optional boolean parameter "C<$orthodox>" is given and true,
  the calendar starts on Sunday instead of Monday.

  =item *

  C<$string = Month_to_Text($month[,$lang]);>

  This function returns the name of the given month in the given or currently
  selected language (see further below for details about the multi-language
  support of this package).

  If the given month lies outside of the valid range from "C<1>" to "C<12>",
  a fatal "month out of range" error will occur.

  =item *

  C<$string = Day_of_Week_to_Text($dow[,$lang]);>

  This function returns the name of the given day of week in the given or
  currently selected language (see further below for details about the
  multi-language support of this package).

  If the given day of week lies outside of the valid range from "C<1>" to "C<7>",
  a fatal "day of week out of range" error will occur.

  =item *

  C<$string = Day_of_Week_Abbreviation($dow[,$lang]);>

  This function returns the special abbreviation of the name of the given
  day of week, B<IF> such special abbreviations have been defined for the
  given or currently selected language (see further below for details
  about the multi-language support of this package).

  (In the original distribution of this package, this was only true for
  Portuguese. Starting with version 5.1, abbreviations for Polish have
  also been introduced. Starting with version 5.7, the abbreviations for
  Portuguese have been disabled. So Polish is currently the only language
  to define such special abbreviations.)

  If not, the first three letters of the name of the day of week in the
  given or currently selected language are returned instead.

  If the given day of week lies outside of the valid range from "C<1>"
  to "C<7>", a fatal "day of week out of range" error will occur.

  Currently, this table of special abbreviations is only used by the
  functions "C<Date_to_Text()>" and "C<Calendar()>", internally.

  =item *

  C<$string = Language_to_Text($lang);>

  This function returns the name of any language supported by this package
  when the internal number representing that language is given as input.

  The original distribution supports the following fourteen languages:

              1   ==>   English                     (default)
              2   ==>   Français    (French)
              3   ==>   Deutsch     (German)
              4   ==>   Español     (Spanish)
              5   ==>   Português   (Portuguese)
              6   ==>   Nederlands  (Dutch)
              7   ==>   Italiano    (Italian)
              8   ==>   Norsk       (Norwegian)
              9   ==>   Svenska     (Swedish)
             10   ==>   Dansk       (Danish)
             11   ==>   suomi       (Finnish)
             12   ==>   Magyar      (Hungarian)
             13   ==>   polski      (Polish)
             14   ==>   Romaneste   (Romanian)

  See the section "How to install additional languages" in the file
  "INSTALL.txt" in this distribution for how to add more languages
  to this package.

  See the description of the function "C<Languages()>" further below
  to determine how many languages are actually available in a given
  installation of this package.

  =item *

  C<$lang = Language();>

  =item *

  C<Language($lang); # DEPRECATED>

  =item *

  C<$oldlang = Language($newlang); # DEPRECATED>

  This function can be used to determine which language is currently selected,
  and to change the selected language (this latter use is deprecated, because
  this global setting may cause conflicts between threads or modules running
  concurrently).

  Thereby, each language has a unique internal number.

  The original distribution contains the following fourteen languages:

              1   ==>   English                     (default)
              2   ==>   Français    (French)
              3   ==>   Deutsch     (German)
              4   ==>   Español     (Spanish)
              5   ==>   Português   (Portuguese)
              6   ==>   Nederlands  (Dutch)
              7   ==>   Italiano    (Italian)
              8   ==>   Norsk       (Norwegian)
              9   ==>   Svenska     (Swedish)
             10   ==>   Dansk       (Danish)
             11   ==>   suomi       (Finnish)
             12   ==>   Magyar      (Hungarian)
             13   ==>   polski      (Polish)
             14   ==>   Romaneste   (Romanian)

  See the section "How to install additional languages" in the file
  "INSTALL.txt" in this distribution for how to add more languages
  to this package.

  See the description of the function "C<Languages()>" further below
  to determine how many languages are actually available in a given
  installation of this package.

  B<BEWARE> that in order for your programs to be portable, you should B<NEVER>
  actually use the internal number of a language in this package B<EXPLICITLY>,
  because the same number could mean different languages on different systems,
  depending on what languages have been added to any given installation of this
  package.

  Therefore, you should always use a statement such as

    Language(Decode_Language("Name_of_Language")); # DEPRECATED

  or

    DateCalc_Function(@parameters,Decode_Language("Name_of_Language")); # RECOMMENDED

  to select the desired language, and

    $language = Language_to_Text(Language());

  or

    $old_language = Language_to_Text(Language("Name_of_new_Language")); # DEPRECATED

  to determine the (previously) selected language.

  If the so chosen language is not available in the current installation,
  this will result in an appropriate error message, instead of silently
  using the wrong (a random) language (which just happens to have the
  same internal number in the other installation).

  B<BEWARE> that when using the function "C<Language()>", the selected
  language is a global setting, shared by all threads or modules you
  might be running concurrently, thus possibly causing conflicts between
  them.

  In order to avoid these conflicts, you should B<NEVER> use the function
  "C<Language()>", but should B<ALWAYS> pass a language number (as returned
  by the function "C<Decode_Language()>") to the functions which are
  language-dependent, which are:

  "Decode_Month()", "Decode_Day_of_Week()", "Compressed_to_Text()",
  "Date_to_Text()", "Date_to_Text_Long()", "Calendar()",
  "Month_to_Text()", "Day_of_Week_to_Text()", "Day_of_Week_Abbreviation()",
  "Decode_Date_EU()", "Decode_Date_US()", "Decode_Date_EU2()",
  "Decode_Date_US2()", "Parse_Date()".

  Note that when you pass an invalid number, such as e.g. zero, or no
  language parameter at all, these functions will revert to their behaviour
  in the versions of this module prior to 6.0, which means that the global
  setting (as set by "C<Language()>") becomes active again (only in case
  of an invalid or missing language parameter!).

  In the C library "DateCalc.c", where omitting a parameter is not an option,
  passing a zero for the language is therefore the recommended way to guarantee
  backward compatibility.

  =item *

  C<$max_lang = Languages();>

  This function returns the (maximum) number of languages which are
  currently available in your installation of this package.

  (This may vary from installation to installation.)

  See the section "How to install additional languages" in the file
  "INSTALL.txt" in this distribution for how to add more languages
  to this package.

  In the original distribution of this package there are fourteen built-in
  languages, therefore the value returned by this function will be "C<14>"
  if no other languages have been added to your particular installation.

  =item *

  C<if (($year,$month,$day) = Decode_Date_EU2($string[,$lang))>

  This function is the Perl equivalent of the function "C<Decode_Date_EU()>"
  (implemented in C), included here merely as an example to demonstrate how
  easy it is to write your own routine in Perl (using regular expressions)
  adapted to your own special needs, should the necessity arise, and intended
  primarily as a basis for your own development.

  In one particular case this Perl version is actually slightly more permissive
  than its C equivalent, as far as the class of permitted intervening (i.e.,
  delimiting) characters is concerned.

  (Can you tell the subtle, almost insignificant difference by looking at
  the code? Or by experimenting? Hint: Try the string "a3b1c64d" with both
  functions.)

  =item *

  C<if (($year,$month,$day) = Decode_Date_US2($string[,$lang))>

  This function is the Perl equivalent of the function "C<Decode_Date_US()>"
  (implemented in C), included here merely as an example to demonstrate how
  easy it is to write your own routine in Perl (using regular expressions)
  adapted to your own special needs, should the necessity arise, and intended
  primarily as a basis for your own development.

  In one particular case this Perl version is actually slightly more permissive
  than its C equivalent.

  (Hint: This is the same difference as with the "C<Decode_Date_EU()>" and
  "C<Decode_Date_EU2()>" pair of functions.)

  In a different case, the C version is a little bit more permissive than its
  Perl equivalent.

  (Can you tell the difference by looking at the code? Or by experimenting?
  Hint: Try the string "(1/364)" with both functions.)

  =item *

  C<if (($year,$month,$day) = Parse_Date($string[,$lang))>

  This function is useful for parsing dates as returned by the UNIX "C<date>"
  command or as found in the headers of e-mail (in order to determine the
  date at which some e-mail has been sent or received, for instance).

  Example #1:

    ($year,$month,$day) = Parse_Date(`/bin/date`);

  Example #2:

    while (<MAIL>)
    {
        if (/^From \S/)
        {
            ($year,$month,$day) = Parse_Date($_);
            ...
        }
        ...
    }

  The function returns an empty list if it can't extract a valid date from
  the input string.

  =item *

  C<$lower = ISO_LC($string);>

  Returns a copy of the given string where all letters of the ISO-Latin-1
  character set have been replaced by their lower case equivalents.

  Similar to Perl's built-in function "C<lc()>" (see L<perlfunc(1)/lc>) but
  for the whole ISO-Latin-1 character set, not just plain ASCII.

  =item *

  C<$upper = ISO_UC($string);>

  Returns a copy of the given string where all letters of the ISO-Latin-1
  character set have been replaced by their upper case equivalents.

  Similar to Perl's built-in function "C<uc()>" (see L<perlfunc(1)/uc>) but
  for the whole ISO-Latin-1 character set, not just plain ASCII.

  =item *

  C<$string = Date::Calc::Version();>

  This function returns a string with the (numeric) version number of the
  S<C library> ("DateCalc.c") at the core of this package (which is also
  (automatically) the version number of the "Calc.xs" file).

  Note that under all normal circumstances, this version number should be
  identical with the one found in the Perl variable "C<$Date::Calc::VERSION>"
  (the version number of the "Calc.pm" file).

  Since this function is not exported, you always have to qualify it explicitly,
  i.e., "C<Date::Calc::Version()>".

  This is to avoid possible name space conflicts with version functions from
  other modules.

  =back


pkgId: 06e908540d8807c8142e9a831bd9c8396c92294bc487f5eb6a09fba6c98cb46e
name: local-perl-DateTime-Format-IBeat
arch: noarch
version: 0.16
epoch: 0
release: 1
summary: DateTime-Format-IBeat - Format times in .beat notation
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Iain Truskett <spoon@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-DateTime-Format-IBeat-0.16-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-DateTime-Format-IBeat-0.16-1.noarch.rpm
checksum_type: sha256
description:
  No Time Zones

  No Geographical Borders

  How long is a Swatch .beat? In short, we have divided up the virtual and
  real day into 1000 I<beats>. One Swatch beat is the equivalent of 1
  minute 26.4 seconds. That means that 12 noon in the old time system is
  the equivalent of @500 Swatch .beats.

  Okay, so how can a surfer in New York, or a passenger on a transatlantic
  flight know when it is @500 Swatch .beats in Central Europe for example?
  How can the New York surfer make a date for a chat with his cyber friend
  in Rome? Easy, Internet Time is the same all over the world.(see
  converter)

  How is this possible? We are not just creating a new way of measuring
  time, we are also creating a new meridian in Biel, Switzerland, home of
  Swatch.

  Biel MeanTime (BMT) is the universal reference for Internet Time. A day
  in Internet Time begins at midnight BMT (@000 Swatch .beats) (Central
  European Wintertime). The meridian is marked for all to see on the
  façade of the Swatch International Headquarters on Jakob-Staempfli
  Street, Biel, Switzerland. So, it is the same time all over the world,
  be it night or day, the era of time zones has disappeared.

  The BMT meridian was inaugurated on 23 October 1998 in the presence of
  Nicholas Negroponte, founder and director of the Massachusetts Institute
  of Technology`s Media Laboratory.

  --- http://www.swatch.com/itime_tools/itime.php


pkgId: b124725126bfcfac8386ec1c086ea4d1e7a065baa825f5eb2bb68455dfb8a71d
name: local-perl-Devel-Cycle
arch: noarch
version: 1.11
epoch: 0
release: 1
summary: Devel-Cycle - Find memory cycles in objects
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Lincoln Stein <lstein@cshl.edu>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Devel-Cycle-1.11-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Devel-Cycle-1.11-1.noarch.rpm
checksum_type: sha256
description:
  This is a simple developer's tool for finding circular references in
  objects and other types of references.  Because of Perl's
  reference-count based memory management, circular references will
  cause memory leaks.


pkgId: 3758924ec31fbf7a125d46bf9cb50c0cf574ab0a5a4b6645373543481270c5c3
name: local-perl-Devel-GlobalDestruction
arch: x86_64
version: 0.04
epoch: 0
release: 1
summary: Devel-GlobalDestruction - Expose the flag which marks global
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Yuval Kogman <Eltnothingmuch@woobling.orgEgt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Devel-GlobalDestruction-0.04-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Devel-GlobalDestruction-0.04-1.x86_64.rpm
checksum_type: sha256
description:
  Perl's global destruction is a little tricky to deal with WRT finalizers
  because it's not ordered and objects can sometimes disappear.

  Writing defensive destructors is hard and annoying, and usually if global
  destruction is happenning you only need the destructors that free up non
  process local resources to actually execute.

  For these constructors you can avoid the mess by simply bailing out if global
  destruction is in effect.


pkgId: 98c45bbfa3637f9d5be0c1219d1d545c3276af9cb07a0cb49a56089f9d6ab60a
name: local-perl-Devel-StackTrace-AsHTML
arch: noarch
version: 0.11
epoch: 0
release: 1
summary: Devel-StackTrace-AsHTML - Displays stack trace in HTML
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tatsuhiko Miyagawa <miyagawa@bulknews.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Devel-StackTrace-AsHTML-0.11-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Devel-StackTrace-AsHTML-0.11-1.noarch.rpm
checksum_type: sha256
description:
  Devel::StackTrace::AsHTML adds C<as_html> method to L<Devel::StackTrace> which
  displays the stack trace in beautiful HTML, with code snippet context and
  function parameters. If you call it on an instance of
  L<Devel::StackTrace::WithLexicals>, you even get to see the lexical variables
  of each stack frame.


pkgId: 87ec4acb7ab8c0e2c5580773feeb57eb0d71a8b2b7c47d1b59196d18b7ec2aa5
name: local-perl-Devel-Symdump
arch: noarch
version: 2.08
epoch: 0
release: 1
summary: Devel-Symdump - dump symbol names or the symbol table
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andreas Koenig F <andk@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Devel-Symdump-2.08-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Devel-Symdump-2.08-1.noarch.rpm
checksum_type: sha256
description:
  This little package serves to access the symbol table of perl.

  =over 4

  =item C<Devel::Symdump-E<gt>rnew(@packages)>

  returns a symbol table object for all subtrees below @packages.
  Nested Modules are analyzed recursively. If no package is given as
  argument, it defaults to C<main>. That means to get the whole symbol
  table, just do a C<rnew> without arguments.

  The global variable $Devel::Symdump::MAX_RECURSION limits the
  recursion to prevent contention. The default value is set to 97, just
  low enough to survive the test suite without a warning about deep
  recursion.

  =item C<Devel::Symdump-E<gt>new(@packages)>

  does not go into recursion and only analyzes the packages that are
  given as arguments.

  =item packages, scalars, arrays, hashes, functions, ios

  The methods packages(), scalars(), arrays(), hashes(), functions(),
  ios(), and (for older perls) unknowns() each return an array of fully
  qualified symbols of the specified type in all packages that are held
  within a Devel::Symdump object, but without the leading C<$>, C<@> or
  C<%>. In a scalar context, they will return the number of such
  symbols. Unknown symbols are usually either formats or variables that
  haven't yet got a defined value.

  =item as_string

  =item as_HTML

  As_string() and as_HTML() return a simple string/HTML representations
  of the object.

  =item diff

  Diff() prints the difference between two Devel::Symdump objects in
  human readable form. The format is similar to the one used by the
  as_string method.

  =item isa_tree

  =item inh_tree

  Isa_tree() and inh_tree() both return a simple string representation
  of the current inheritance tree. The difference between the two
  methods is the direction from which the tree is viewed: top-down or
  bottom-up. As I'm sure, many users will have different expectation
  about what is top and what is bottom, I'll provide an example what
  happens when the Socket module is loaded:

  =item % print Devel::Symdump-E<gt>inh_tree

      AutoLoader
              DynaLoader
                      Socket
      DynaLoader
              Socket
      Exporter
              Carp
              Config
              Socket

  The inh_tree method shows on the left hand side a package name and
  indented to the right the packages that use the former.

  =item % print Devel::Symdump-E<gt>isa_tree

      Carp
              Exporter
      Config
              Exporter
      DynaLoader
              AutoLoader
      Socket
              Exporter
              DynaLoader
                      AutoLoader

  The isa_tree method displays from left to right ISA relationships, so
  Socket IS A DynaLoader and DynaLoader IS A AutoLoader. (Actually, they
  were at the time this manpage was written)

  =back

  You may call both methods, isa_tree() and inh_tree(), with an
  object. If you do that, the object will store the output and retrieve
  it when you call the same method again later. The typical usage would
  be to use them as class methods directly though.


pkgId: ca85cec9367beae75706e1678e950cad38a605e946e80a3c6ee31bd5def25528
name: local-perl-Digest-HMAC
arch: noarch
version: 1.02
epoch: 0
release: 1
summary: Digest-HMAC - Keyed-Hashing for Message Authentication
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Digest-HMAC-1.02-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Digest-HMAC-1.02-1.noarch.rpm
checksum_type: sha256
description:
  HMAC is used for message integrity checks between two parties that
  share a secret key, and works in combination with some other Digest
  algorithm, usually MD5 or SHA-1.  The HMAC mechanism is described in
  RFC 2104.

  HMAC follow the common C<Digest::> interface, but the constructor
  takes the secret key and the name of some other simple C<Digest::>
  as argument.


pkgId: 23eb32ab1ac4aedad4e8ce52456fd51543b70e67617b6af033e1943ecc15a998
name: local-perl-Digest-Perl-MD5
arch: noarch
version: 1.8
epoch: 0
release: 1
summary: Digest-Perl-MD5 - Perl Implementation of Rivest's MD5 algorithm
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Christian Lackas <delta@clackas.de>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Digest-Perl-MD5-1.8-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Digest-Perl-MD5-1.8-1.noarch.rpm
checksum_type: sha256
description:
  This modules has the same interface as the much faster C<Digest::MD5>. So you can
  easily exchange them, e.g.

  	BEGIN {
  	  eval {
  	    require Digest::MD5;
  	    import Digest::MD5 'md5_hex'
  	  };
  	  if ($@) { # ups, no Digest::MD5
  	    require Digest::Perl::MD5;
  	    import Digest::Perl::MD5 'md5_hex'
  	  }
  	}

  If the C<Digest::MD5> module is available it is used and if not you take
  C<Digest::Perl::MD5>.

  You can also install the Perl part of Digest::MD5 together with Digest::Perl::MD5
  and use Digest::MD5 as normal, it falls back to Digest::Perl::MD5 if it
  cannot load its object files.

  For a detailed Documentation see the C<Digest::MD5> module.


pkgId: 4ce906a7249ba09770bd50202e4a56f02bd534c824b90fbed1f1aade826e693f
name: local-perl-Digest-SHA
arch: x86_64
version: 5.61
epoch: 1
release: 162.ep
summary: Perl extension for SHA-1/224/256/384/512
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Digest-SHA-5.61-162.ep.x86_64.rpm
checksum_type: sha256
description:
  Digest::SHA is a complete implementation of the NIST Secure Hash
  Standard.  It gives Perl programmers a convenient way to calculate
  SHA-1, SHA-224, SHA-256, SHA-384, and SHA-512 message digests.  The
  module can handle all types of input, including partial-byte data.


pkgId: 5eab7e9372cf417e86700a67dba9647e09d151488fc155c46dcef864d893a5e4
name: local-perl-Digest-SHA1
arch: x86_64
version: 2.13
epoch: 0
release: 1
summary: Digest-SHA1 - Perl interface to the SHA-1 algorithm
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Digest-SHA1-2.13-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Digest-SHA1-2.13-1.x86_64.rpm
checksum_type: sha256
description:
  The C<Digest::SHA1> module allows you to use the NIST SHA-1 message
  digest algorithm from within Perl programs.  The algorithm takes as
  input a message of arbitrary length and produces as output a 160-bit
  "fingerprint" or "message digest" of the input.

  In 2005, security flaws were identified in SHA-1, namely that a possible
  mathematical weakness might exist, indicating that a stronger hash function
  would be desirable.  The L<Digest::SHA> module implements the stronger
  algorithms in the SHA family.

  The C<Digest::SHA1> module provide a procedural interface for simple
  use, as well as an object oriented interface that can handle messages
  of arbitrary length and which can read files directly.


pkgId: 8fe189edcb0cd693d5f01a1585576fba7f1f4db9be12868cda8a3fe0e6bafb4f
name: local-perl-Email-Address
arch: noarch
version: 1.892
epoch: 0
release: 1
summary: Email-Address - RFC 2822 Address Parsing
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Casey West <casey@geeknest.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Email-Address-1.892-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Email-Address-1.892-1.noarch.rpm
checksum_type: sha256
description:
  This class implements a regex-based RFC 2822 parser that locates email
  addresses in strings and returns a list of C<Email::Address> objects found.
  Alternatley you may construct objects manually. The goal of this software is to
  be correct, and very very fast.


pkgId: a6bc38899e713d858118c019c238cbc35cfb06a94afb9757fd24219c8bde05fb
name: local-perl-Email-Date-Format
arch: noarch
version: 1.002
epoch: 0
release: 1
summary: Email-Date-Format - produce RFC 8822 date strings
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ricardo SIGNES <rjbs@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Email-Date-Format-1.002-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Email-Date-Format-1.002-1.noarch.rpm
checksum_type: sha256
description:
  This module provides a simple means for generating an RFC 2822 compliant
  datetime string.  (In case you care, they're not RFC 822 dates, because they
  use a four digit year, which is not allowed in RFC 822.)


pkgId: 4834ffc4724a5077141af9a82dbb331034ac076478596ca24c14351631fd4f78
name: local-perl-Email-MIME
arch: noarch
version: 1.910
epoch: 0
release: 1
summary: Email-MIME - Easy MIME message parsing.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Casey West <Ccasey@geeknest.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Email-MIME-1.910-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Email-MIME-1.910-1.noarch.rpm
checksum_type: sha256
description:
  This is an extension of the L<Email::Simple> module, to handle MIME
  encoded messages. It takes a message as a string, splits it up into its
  constituent parts, and allows you access to various parts of the
  message. Headers are decoded from MIME encoding.


pkgId: 7cf7c0c24229554b995fb4f5229b78da9a983542a5c2d1afb884be72690c25ad
name: local-perl-Email-MIME-ContentType
arch: noarch
version: 1.015
epoch: 0
release: 1
summary: Email-MIME-ContentType - Parse a MIME Content-Type Header
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Simon Cozens <simon@nonet>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Email-MIME-ContentType-1.015-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Email-MIME-ContentType-1.015-1.noarch.rpm
checksum_type: sha256
description:
  use Email::MIME::ContentType;

    
    my $ct = 'text/plain; charset="us-ascii"; format=flowed';
    my $data = parse_content_type($ct);

    $data = {
      discrete   => "text",
      composite  => "plain",
      attributes => {
        charset => "us-ascii",
        format  => "flowed"
      }
    };


pkgId: 19d9f42a7cfece8f169aeb4ea8a31e2ea1dd724259db57d2946067a424693b7e
name: local-perl-Email-MIME-Encodings
arch: noarch
version: 1.313
epoch: 0
release: 1
summary: Email-MIME-Encodings - A unified interface to MIME encoding and decoding
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Simon Cozens <Csimon@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Email-MIME-Encodings-1.313-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Email-MIME-Encodings-1.313-1.noarch.rpm
checksum_type: sha256
description:
  This module simply wraps C<MIME::Base64> and C<MIME::QuotedPrint>
  so that you can throw the contents of a C<Content-Transfer-Encoding>
  header at some text and have the right thing happen.


pkgId: 5a6a8e5a095f9ab829d93a4aae748996f6adc5c456454f3fcc0ab0b84f851d52
name: local-perl-Email-MessageID
arch: noarch
version: 1.402
epoch: 0
release: 1
summary: Email-MessageID - Generate world unique message-ids
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Casey West <casey@geeknest.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Email-MessageID-1.402-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Email-MessageID-1.402-1.noarch.rpm
checksum_type: sha256
description:
  Message-ids are optional, but highly recommended, headers that identify a
  message uniquely. This software generates a unique message-id.


pkgId: 75bc6e5e53456496c0d1aa7e52da2c53ab49b269721700ef6023b9b4d45ddbaa
name: local-perl-Email-Send
arch: noarch
version: 2.198
epoch: 0
release: 1
summary: Email-Send - Simply Sending Email
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Casey West <casey@geeknest.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Email-Send-2.198-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Email-Send-2.198-1.noarch.rpm
checksum_type: sha256
description:
  This module provides a very simple, very clean, very specific interface
  to multiple Email mailers. The goal of this software is to be small
  and simple, easy to use, and easy to extend.


pkgId: 4e501f9c97a4b1a2d730d73b67b3855ee53e1655f3a78547c418856cb35b914f
name: local-perl-Email-Simple
arch: noarch
version: 2.100
epoch: 0
release: 1
summary: Email-Simple - simple parsing of RFC2822 message format and headers
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Simon Cozens originally <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Email-Simple-2.100-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Email-Simple-2.100-1.noarch.rpm
checksum_type: sha256
description:
  C<Email::Simple> is the first deliverable of the "Perl Email Project."  The
  Email:: namespace was begun as a reaction against the increasing complexity and
  bugginess of Perl's existing email modules.  C<Email::*> modules are meant to
  be simple to use and to maintain, pared to the bone, fast, minimal in their
  external dependencies, and correct.


pkgId: b6839a5c9a41bd218bd03dfd73ba227c514a59487b27b88b553dcf8fc1f43be9
name: local-perl-Encode-IMAPUTF7
arch: noarch
version: 1.05
epoch: 0
release: 1
summary: Encode-IMAPUTF7 - modification of UTF-7 encoding for IMAP
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Peter Makholm <peter@makholm.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Encode-IMAPUTF7-1.05-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Encode-IMAPUTF7-1.05-1.noarch.rpm
checksum_type: sha256
description:
  use Encode qw/encode decode/;

    print encode('IMAP-UTF-7', 'Répertoire');
    print decode('IMAP-UTF-7', R&AOk-pertoire');


pkgId: 48dcb47a305e5d1892d3cf4cc8a0b94b41c283239479023864dd1db4fc27d848
name: local-perl-Encode-Locale
arch: noarch
version: 1.02
epoch: 0
release: 1
summary: Encode-Locale - Determine the locale encoding
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Encode-Locale-1.02-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Encode-Locale-1.02-1.noarch.rpm
checksum_type: sha256
description:
  In many applications it's wise to let Perl use Unicode for the strings it
  processes.  Most of the interfaces Perl has to the outside world is still byte
  based.  Programs therefore needs to decode byte strings that enter the program
  from the outside and encode them again on the way out.

  The POSIX locale system is used to specify both the language conventions
  requested by the user and the preferred character set to consume and
  output.  The C<Encode::Locale> module looks up the charset and encoding (called
  a CODESET in the locale jargon) and arrange for the L<Encode> module to know
  this encoding under the name "locale".  It means bytes obtained from the
  environment can be converted to Unicode strings by calling C<<
  Encode::encode(locale => $bytes) >> and converted back again with C<<
  Encode::decode(locale => $string) >>.

  Where file systems interfaces pass file names in and out of the program we also
  need care.  The trend is for operating systems to use a fixed file encoding
  that don't actually depend on the locale; and this module determines the most
  appropriate encoding for file names. The L<Encode> module will know this
  encoding under the name "locale_fs".  For traditional Unix systems this will
  be an alias to the same encoding as "locale".

  For programs running in a terminal window (called a "Console" on some systems)
  the "locale" encoding is usually a good choice for what to expect as input and
  output.  Some systems allows us to query the encoding set for the terminal and
  C<Encode::Locale> will do that if available and make these encodings known
  under the C<Encode> aliases "console_in" and "console_out".  For systems where
  we can't determine the terminal encoding these will be aliased as the same
  encoding as "locale".  The advice is to use "console_in" for input known to
  come from the terminal and "console_out" for output known to go from the
  terminal.

  In addition to arranging for various Encode aliases the following functions and
  variables are provided:

  =over

  =item decode_argv( )

  =item decode_argv( Encode::FB_CROAK )

  This will decode the command line arguments to perl (the C<@ARGV> array) in-place.

  The function will by default replace characters that can't be decoded by
  "\x{FFFD}", the Unicode replacement character.

  Any argument provided is passed as CHECK to underlying Encode::decode() call.
  Pass the value C<Encode::FB_CROAK> to have the decoding croak if not all the
  command line arguments can be decoded.  See L<Encode/"Handling Malformed Data">
  for details on other options for CHECK.

  =item env( $uni_key )

  =item env( $uni_key => $uni_value )

  Interface to get/set environment variables.  Returns the current value as a
  Unicode string. The $uni_key and $uni_value arguments are expected to be
  Unicode strings as well.  Passing C<undef> as $uni_value deletes the
  environment variable named $uni_key.

  The returned value will have the characters that can't be decoded replaced by
  "\x{FFFD}", the Unicode replacement character.

  There is no interface to request alternative CHECK behavior as for
  decode_argv().  If you need that you need to call encode/decode yourself.
  For example:

      my $key = Encode::encode(locale => $uni_key, Encode::FB_CROAK);
      my $uni_value = Encode::decode(locale => $ENV{$key}, Encode::FB_CROAK);

  =item reinit( )

  =item reinit( $encoding )

  Reinitialize the encodings from the locale.  You want to call this function if
  you changed anything in the environment that might influence the locale.

  This function will croak if the determined encoding isn't recognized by
  the Encode module.

  With argument force $ENCODING_... variables to set to the given value.

  =item $ENCODING_LOCALE

  The encoding name determined to be suitable for the current locale.
  L<Encode> know this encoding as "locale".

  =item $ENCODING_LOCALE_FS

  The encoding name determined to be suiteable for file system interfaces
  involving file names.
  L<Encode> know this encoding as "locale_fs".

  =item $ENCODING_CONSOLE_IN

  =item $ENCODING_CONSOLE_OUT

  The encodings to be used for reading and writing output to the a console.
  L<Encode> know these encodings as "console_in" and "console_out".

  =back


pkgId: 5ef4b12710989804eeb6d0de18e6fedf37bf72b66ec3471a942a907257ffc486
name: local-perl-ExtUtils-CBuilder
arch: noarch
version: 0.280203
epoch: 1
release: 162.ep
summary: Compile and link C code for Perl modules
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-ExtUtils-CBuilder-0.280203-162.ep.noarch.rpm
checksum_type: sha256
description:
  This module can build the C portions of Perl modules by invoking the
  appropriate compilers and linkers in a cross-platform manner. It was motivated
  by the Module::Build project, but may be useful for other purposes as well.


pkgId: 81a65f487068016865d5bb30ecb6776f5f74b3b400eaa7c415fbeee333863f76
name: local-perl-ExtUtils-ParseXS
arch: noarch
version: 2.2210
epoch: 1
release: 162.ep
summary: Module and a script for converting Perl XS code into C code
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-ExtUtils-ParseXS-2.2210-162.ep.noarch.rpm
checksum_type: sha256
description:
  ExtUtils::ParseXS will compile XS code into C code by embedding the constructs
  necessary to let C functions manipulate Perl values and creates the glue
  necessary to let Perl access those functions.


pkgId: 64e5cd1e83a44a6120ada150c8dad64f8c827693714acdb3cc4109c1bea27d38
name: local-perl-File-Find-Rule
arch: noarch
version: 0.33
epoch: 0
release: 1
summary: File-Find-Rule - Alternative interface to File::Find
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Richard Clamp <richardc@unixbeard.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-File-Find-Rule-0.33-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-File-Find-Rule-0.33-1.noarch.rpm
checksum_type: sha256
description:
  File::Find::Rule is a friendlier interface to File::Find.  It allows
  you to build rules which specify the desired files and directories.


pkgId: e2e2d4ee43a6264793dd321526a1102049679d3f3128d86ed11991e546726b9d
name: local-perl-File-Listing
arch: noarch
version: 6.02
epoch: 0
release: 1
summary: File-Listing - parse directory listing
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-File-Listing-6.02-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-File-Listing-6.02-1.noarch.rpm
checksum_type: sha256
description:
  This module exports a single function called parse_dir(), which can be
  used to parse directory listings.

  The first parameter to parse_dir() is the directory listing to parse.
  It can be a scalar, a reference to an array of directory lines or a
  glob representing a filehandle to read the directory listing from.

  The second parameter is the time zone to use when parsing time stamps
  in the listing. If this value is undefined, then the local time zone is
  assumed.

  The third parameter is the type of listing to assume.  Currently
  supported formats are 'unix', 'apache' and 'dosftp'.  The default
  value 'unix'.  Ideally, the listing type should be determined
  automatically.

  The fourth parameter specifies how unparseable lines should be treated.
  Values can be 'ignore', 'warn' or a code reference.  Warn means that
  the perl warn() function will be called.  If a code reference is
  passed, then this routine will be called and the return value from it
  will be incorporated in the listing.  The default is 'ignore'.

  Only the first parameter is mandatory.

  The return value from parse_dir() is a list of directory entries.  In
  a scalar context the return value is a reference to the list.  The
  directory entries are represented by an array consisting of [
  $filename, $filetype, $filesize, $filetime, $filemode ].  The
  $filetype value is one of the letters 'f', 'd', 'l' or '?'.  The
  $filetime value is the seconds since Jan 1, 1970.  The
  $filemode is a bitmask like the mode returned by stat().


pkgId: e57a260a02acaae5f02b5853e18aa9ba6714ffca0fda69edd4f698d7314ee074
name: local-perl-File-Next
arch: x86_64
version: 1.06
epoch: 0
release: 1
summary: File-Next - File-finding iterator
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Lester <andy@petdance.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-File-Next-1.06-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-File-Next-1.06-1.x86_64.rpm
checksum_type: sha256
description:
  File::Next is a lightweight, taint-safe file-finding module.
  It's lightweight and has no non-core prerequisites.

      use File::Next;

      my $files = File::Next::files( '/tmp' );

      while ( defined ( my $file = $files->() ) ) {
          
      }


pkgId: 4bf9c5eb40851da67388369200b95d06aca6fc764d4315809ddd76c1dcb178a9
name: local-perl-File-ShareDir
arch: noarch
version: 1.03
epoch: 0
release: 1
summary: File-ShareDir - Locate per-dist and per-module shared files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Adam Kennedy <adamk@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-File-ShareDir-1.03-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-File-ShareDir-1.03-1.noarch.rpm
checksum_type: sha256
description:
  The intent of L<File::ShareDir> is to provide a companion to
  L<Class::Inspector> and L<File::HomeDir>, modules that take a
  process that is well-known by advanced Perl developers but gets a
  little tricky, and make it more available to the larger Perl community.

  Quite often you want or need your Perl module (CPAN or otherwise)
  to have access to a large amount of read-only data that is stored
  on the file-system at run-time.

  On a linux-like system, this would be in a place such as /usr/share,
  however Perl runs on a wide variety of different systems, and so
  the use of any one location is unreliable.

  Perl provides a little-known method for doing this, but almost
  nobody is aware that it exists. As a result, module authors often
  go through some very strange ways to make the data available to
  their code.

  The most common of these is to dump the data out to an enormous
  Perl data structure and save it into the module itself. The
  result are enormous multi-megabyte .pm files that chew up a
  lot of memory needlessly.

  Another method is to put the data "file" after the __DATA__ compiler
  tag and limit yourself to access as a filehandle.

  The problem to solve is really quite simple.

    1. Write the data files to the system at install time.

    2. Know where you put them at run-time.

  Perl's install system creates an "auto" directory for both
  every distribution and for every module file.

  These are used by a couple of different auto-loading systems
  to store code fragments generated at install time, and various
  other modules written by the Perl "ancient masters".

  But the same mechanism is available to any dist or module to
  store any sort of data.


pkgId: 1f4f5963f57fd8d726e2f8c1fe4f92e001cd751c7b270fefc4ebf7fd67e3dbbb
name: local-perl-File-Slurp
arch: noarch
version: 9999.19
epoch: 0
release: 1
summary: File-Slurp - Simple and Efficient Reading/Writing/Modifying of Complete Files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Uri Guttman <uri@stemsystems.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-File-Slurp-9999.19-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-File-Slurp-9999.19-1.noarch.rpm
checksum_type: sha256
description:
  This module provides subs that allow you to read or write entire files
  with one simple call. They are designed to be simple to use, have
  flexible ways to pass in or get the file contents and to be very
  efficient.  There is also a sub to read in all the files in a
  directory other than C<.> and C<..>

  These slurp/spew subs work for files, pipes and sockets, stdio,
  pseudo-files, and the DATA handle. Read more about why slurping files is
  a good thing in the file 'slurp_article.pod' in the extras/ directory.

  If you are interested in how fast these calls work, check out the
  slurp_bench.pl program in the extras/ directory. It compares many
  different forms of slurping. You can select the I/O direction, context
  and file sizes. Use the --help option to see how to run it.


pkgId: dcd09ae12eee1120dd9b6a7134edf5ae34f6518e71351946eecda94c5655897c
name: local-perl-Filesys-Notify-Simple
arch: noarch
version: 0.08
epoch: 0
release: 1
summary: Filesys-Notify-Simple - Simple and dumb file system watcher
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tatsuhiko Miyagawa <miyagawa@bulknews.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Filesys-Notify-Simple-0.08-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Filesys-Notify-Simple-0.08-1.noarch.rpm
checksum_type: sha256
description:
  Filesys::Notify::Simple is a simple but unified interface to get
  notifications of changes to a given filesystem path. It utilizes
  inotify2 on Linux and fsevents on OS X if they're installed, with a
  fallback to the full directory scan if they're not available.

  There are some limitations in this module. If you don't like it, use
  L<File::ChangeNotify>.

  =over 4

  =item *

  There is no file name based filter. Do it in your own code.

  =item *

  You can not get types of events (created, updated, deleted).

  =item *

  Currently C<wait> method blocks.

  =back

  In return, this module doesn't depend on any non-core
  modules. Platform specific optimizations with L<Linux::Inotify2> and
  L<Mac::FSEvents> are truely optional.


pkgId: 25ea478f454105c287410cceeb70b31bb03bf6165eabb98ed0795710d9036ead
name: local-perl-Font-AFM
arch: noarch
version: 1.20
epoch: 0
release: 1
summary: Font-AFM - Interface to Adobe Font Metrics files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: gaas@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Font-AFM-1.20-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Font-AFM-1.20-1.noarch.rpm
checksum_type: sha256
description:
  This module implements the Font::AFM class. Objects of this class are
  initialised from an AFM (Adobe Font Metrics) file and allow you to obtain information
  about the font and the metrics of the various glyphs in the font.

  All measurements in AFM files are given in terms of units equal to
  1/1000 of the scale factor of the font being used. To compute actual
  sizes in a document, these amounts should be multiplied by (scale
  factor of font)/1000.

  The following methods are available:

  =over 3

  =item $afm = Font::AFM->new($fontname)

  Object constructor. Takes the name of the font as argument.
  Croaks if the font can not be found.

  =item $afm->latin1_wx_table()

  Returns a 256-element array, where each element contains the width
  of the corresponding character in the iso-8859-1 character set.

  =item $afm->stringwidth($string, [$fontsize])

  Returns the width of the argument string. The string is
  assumed to be encoded in the iso-8859-1 character set.  A second
  argument can be used to scale the width according to the font size.

  =item $afm->FontName

  The name of the font as presented to the PostScript language
  C<findfont> operator, for instance "Times-Roman".

  =item $afm->FullName

  Unique, human-readable name for an individual font, for instance
  "Times Roman".

  =item $afm->FamilyName

  Human-readable name for a group of fonts that are stylistic variants
  of a single design. All fonts that are members of such a group should
  have exactly the same C<FamilyName>. Example of a family name is
  "Times".

  =item $afm->Weight

  Human-readable name for the weight, or "boldness", attribute of a font.
  Examples are C<Roman>, C<Bold>, C<Light>.

  =item $afm->ItalicAngle

  Angle in degrees counterclockwise from the vertical of the dominant
  vertical strokes of the font.

  =item $afm->IsFixedPitch

  If C<true>, the font is a fixed-pitch
  (monospaced) font.

  =item $afm->FontBBox

  A string of four numbers giving the lower-left x, lower-left y,
  upper-right x, and upper-right y of the font bounding box. The font
  bounding box is the smallest rectangle enclosing the shape that would
  result if all the characters of the font were placed with their
  origins coincident, and then painted.

  =item $afm->UnderlinePosition

  Recommended distance from the baseline for positioning underline
  strokes. This number is the y coordinate of the center of the stroke.

  =item $afm->UnderlineThickness

  Recommended stroke width for underlining.

  =item $afm->Version

  Version number of the font.

  =item $afm->Notice

  Trademark or copyright notice, if applicable.

  =item $afm->Comment

  Comments found in the AFM file.

  =item $afm->EncodingScheme

  The name of the standard encoding scheme for the font. Most Adobe
  fonts use the C<AdobeStandardEncoding>. Special fonts might state
  C<FontSpecific>.

  =item $afm->CapHeight

  Usually the y-value of the top of the capital H.

  =item $afm->XHeight

  Typically the y-value of the top of the lowercase x.

  =item $afm->Ascender

  Typically the y-value of the top of the lowercase d.

  =item $afm->Descender

  Typically the y-value of the bottom of the lowercase p.

  =item $afm->Wx

  Returns a hash table that maps from glyph names to the width of that glyph.

  =item $afm->BBox

  Returns a hash table that maps from glyph names to bounding box information.
  The bounding box consist of four numbers: llx, lly, urx, ury.

  =item $afm->dump

  Dumps the content of the Font::AFM object to STDOUT.  Might sometimes
  be useful for debugging.

  =back


  The AFM specification can be found at:

     http://partners.adobe.com/asn/developer/pdfs/tn/5004.AFM_Spec.pdf


pkgId: b82354c1354dcd9c6577a8ee7667319e09d9b715179cd493f1c30477ac2e50d1
name: local-perl-Forward-Routes
arch: noarch
version: 0.51
epoch: 0
release: 1
summary: Forward-Routes - Forward::Routes: routes for web framework builders
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: ForwardEver <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Forward-Routes-0.51-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Forward-Routes-0.51-1.noarch.rpm
checksum_type: sha256
description:
  Instead of letting a web server like Apache decide which files to serve based
  on the provided URL, the whole work can be done by your framework using the
  L<Forward::Routes> module.

  Ruby on Rails and Perl's Mojolicious make use of routes. Forward::Routes, in
  contrast to that, tries to provide the same or even better functionality
  without the tight couplings with a full featured framework.

  Think of routes as kind of simplified regular expressions! First of all, a
  bunch of routes is defined. Each route contains information on

  =over 2

  =item *

  what kind of URLs to match

  =item *

  what to do in case of a match

  =back

  Finally, the request method and path of a users HTTP request are passed to
  search for a matching route.


pkgId: 0a9d7de253443cf3fe244277b5d698825ae6055e5ac5d4b1b5a378531541cfec
name: local-perl-FreezeThaw
arch: noarch
version: 0.5001
epoch: 0
release: 1
summary: FreezeThaw - converting Perl structures to strings and back.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ilya Zakharevich <ilyaz@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-FreezeThaw-0.5001-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-FreezeThaw-0.5001-1.noarch.rpm
checksum_type: sha256
description:
  Converts data to/from stringified form, appropriate for
  saving-to/reading-from permanent storage.

  Deals with objects, circular lists, repeated appearence of the same
  refence. Does not deal with overloaded I<stringify> operator yet.


pkgId: bcf157261711be7351e94b866c6696d8e85493e3fffe0fe86b44d2fff9fe73ee
name: local-perl-GD
arch: x86_64
version: 2.46
epoch: 0
release: 1
summary: GD - Interface to Gd Graphics Library
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Lincoln Stein (lstein@cshl.org)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-GD-2.46-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-GD-2.46-1.x86_64.rpm
checksum_type: sha256
description:
  B<GD.pm> is a Perl interface to Thomas Boutell's gd graphics library
  (version 2.01 or higher; see below). GD allows you to create color
  drawings using a large number of graphics primitives, and emit the
  drawings as PNG files.

  GD defines the following four classes:

  =over 5


  =item C<GD::Image>

  An image class, which holds the image data and accepts graphic
  primitive method calls.

  =item C<GD::Font>

  A font class, which holds static font information and used for text
  rendering.

  =item C<GD::Polygon>

  A simple polygon object, used for storing lists of vertices prior to
  rendering a polygon into an image.

  =item C<GD::Simple>

  A "simple" class that simplifies the GD::Image API and then adds a set
  of object-oriented drawing methods using turtle graphics, simplified
  font handling, ability to work in polar coordinates, HSV color spaces,
  and human-readable color names like "lightblue". Please see
  L<GD::Simple> for a description of these methods.

  =back

  A Simple Example:

  	

  	use GD;

  	
  	$im = new GD::Image(100,100);

  	
  	$white = $im->colorAllocate(255,255,255);
  	$black = $im->colorAllocate(0,0,0);
  	$red = $im->colorAllocate(255,0,0);
  	$blue = $im->colorAllocate(0,0,255);

  	
  	$im->transparent($white);
  	$im->interlaced('true');

  	
  	$im->rectangle(0,0,99,99,$black);

  	
  	$im->arc(50,50,95,75,0,360,$blue);

  	
  	$im->fill(50,50,$red);

  	
  	binmode STDOUT;

  	
  	print $im->png;

  Notes:

  =over 5

  =item 1.
  To create a new, empty image, send a new() message to GD::Image, passing
  it the width and height of the image you want to create.  An image
  object will be returned.  Other class methods allow you to initialize
  an image from a preexisting JPG, PNG, GD, GD2 or XBM file.

  =item 2.
  Next you will ordinarily add colors to the image's color table.
  colors are added using a colorAllocate() method call.  The three
  parameters in each call are the red, green and blue (rgb) triples for
  the desired color.  The method returns the index of that color in the
  image's color table.  You should store these indexes for later use.

  =item 3.
  Now you can do some drawing!  The various graphics primitives are
  described below.  In this example, we do some text drawing, create an
  oval, and create and draw a polygon.

  =item 4.
  Polygons are created with a new() message to GD::Polygon.  You can add
  points to the returned polygon one at a time using the addPt() method.
  The polygon can then be passed to an image for rendering.

  =item 5.
  When you're done drawing, you can convert the image into PNG format by
  sending it a png() message.  It will return a (potentially large)
  scalar value containing the binary data for the image.  Ordinarily you
  will print it out at this point or write it to a file.  To ensure
  portability to platforms that differentiate between text and binary
  files, be sure to call C<binmode()> on the file you are writing
  the image to.

  =back


pkgId: 33d3344953259cdd9d6e264faade6400de4f709eb55913d55f7dc25887be6e67
name: local-perl-GD-Barcode
arch: noarch
version: 1.15
epoch: 0
release: 1
summary: GD-Barcode - Create barcode image with GD
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Kawai Takanori <GCD00051@nifty.ne.jp>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-GD-Barcode-1.15-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-GD-Barcode-1.15-1.noarch.rpm
checksum_type: sha256
description:
  GD::Barcode is a subclass of GD and allows you to create barcode image with GD.
  This module based on "Generate Barcode Ver 1.02 By Shisei Hanai 97/08/22".

  From 1.14, you can use this module even if no GD (except plot method).


pkgId: 0cc733732605da4b41e783039dbc215a191f843b12865a4b8afa740f2b6e10b9
name: local-perl-GDGraph
arch: noarch
version: 1.44_01
epoch: 0
release: 1
summary: GDGraph - Produces charts with GD
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Martien Verbruggen <mgjv@tradingpost.com.au>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-GDGraph-1.44_01-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-GDGraph-1.44_01-1.noarch.rpm
checksum_type: sha256
description:
  B<GD::Graph> is a I<perl5> module to create charts using the GD module.
  The following classes for graphs with axes are defined:

  =over 4

  =item C<GD::Graph::lines>

  Create a line chart.

  =item C<GD::Graph::bars> and C<GD::Graph::hbars>

  Create a bar chart with vertical or horizontal bars.

  =item C<GD::Graph::points>

  Create an chart, displaying the data as points.

  =item C<GD::Graph::linespoints>

  Combination of lines and points.

  =item C<GD::Graph::area>

  Create a graph, representing the data as areas under a line.

  =item C<GD::Graph::mixed>

  Create a mixed type graph, any combination of the above. At the moment
  this is fairly limited. Some of the options that can be used with some
  of the individual graph types won't work very well. Bar graphs drawn
  after lines or points graphs may obscure the earlier data, and
  specifying bar_width will not produce the results you probably expected.

  =back

  Additional types:

  =over 4

  =item C<GD::Graph::pie>

  Create a pie chart.

  =back


pkgId: efa5d9bcec1e32e707bd2d059757e60f06cf5944cc9fc03e31fd18f27ab96344
name: local-perl-GDTextUtil
arch: noarch
version: 0.86
epoch: 0
release: 1
summary: GDTextUtil - text utilities for GD
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Martien Verbruggen (mgjv@comdyn.com.au)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-GDTextUtil-0.86-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-GDTextUtil-0.86-1.noarch.rpm
checksum_type: sha256
description:
  This module provides a font-independent way of dealing with text in
  GD, for use with the GD::Text::* modules and GD::Graph.


pkgId: c43d315251436bff49dcecc775a0c76e6bb19b217883106a7b2e1c251b9cc9a7
name: local-perl-GSSAPI
arch: x86_64
version: 0.28
epoch: 0
release: 1
summary: GSSAPI - Perl extension providing access to the GSSAPIv2 library
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Achim Grolms <perl@grolmsnet.de>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-GSSAPI-0.28-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-GSSAPI-0.28-1.x86_64.rpm
checksum_type: sha256
description:
  This module gives access to the routines of the GSSAPI library,
  as described in rfc2743 and rfc2744 and implemented by the
  Kerberos-1.2 distribution from MIT.

  Since 0.14 it also compiles and works with Heimdal.
  Lacks of Heimdal support are gss_release_oid(),
  gss_str_to_oid() and fail of some tests.
  Have a look at the tests in t/ directory too see what tests
  fail on Heimdal ( the *.t tests are just skipping them at the moment)

  The API presented by this module is a mildly object oriented
  reinterpretation of the C API, where opaque C structures are
  Perl objects, but the style of function call has been left
  mostly untouched.  As a result, most routines modify one or
  more of the parameters passed to them, reflecting the C
  call-by-reference (or call-by-value-return) semantics.

  All users of this module are therefore strongly advised to
  localize all usage of these routines to minimize pain if and
  when the API changes.


pkgId: 2bb517c5c9379bbec4835aa9e737fcca7753d17c35533315c6666854d219375d
name: local-perl-HTML-Form
arch: noarch
version: 6.00
epoch: 0
release: 1
summary: HTML-Form - Class that represents an HTML form element
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTML-Form-6.00-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTML-Form-6.00-1.noarch.rpm
checksum_type: sha256
description:
  Objects of the C<HTML::Form> class represents a single HTML
  C<E<lt>formE<gt> ... E<lt>/formE<gt>> instance.  A form consists of a
  sequence of inputs that usually have names, and which can take on
  various values.  The state of a form can be tweaked and it can then be
  asked to provide C<HTTP::Request> objects that can be passed to the
  request() method of C<LWP::UserAgent>.

  The following methods are available:

  =over 4

  =item @forms = HTML::Form->parse( $html_document, $base_uri )

  =item @forms = HTML::Form->parse( $html_document, base => $base_uri, %opt )

  =item @forms = HTML::Form->parse( $response, %opt )

  The parse() class method will parse an HTML document and build up
  C<HTML::Form> objects for each <form> element found.  If called in scalar
  context only returns the first <form>.  Returns an empty list if there
  are no forms to be found.

  The required arguments is the HTML document to parse ($html_document) and the
  URI used to retrieve the document ($base_uri).  The base URI is needed to resolve
  relative action URIs.  The provided HTML document should be a Unicode string
  (or US-ASCII).

  By default HTML::Form assumes that the original document was UTF-8 encoded and
  thus encode forms that don't specify an explict I<accept-charset> as UTF-8.
  The charset assumed can be overridden by providing the C<charset> option to
  parse().  It's a good idea to be explict about this parameter as well, thus
  the recommended simplest invocation becomes:

      my @forms = HTML::Form->parse(
          Encode::decode($encoding, $html_document_bytes),
          base => $base_uri,
  	charset => $encoding,
      );

  If the document was retrieved with LWP then the response object provide methods
  to obtain a proper value for C<base> and C<charset>:

      my $ua = LWP::UserAgent->new;
      my $response = $ua->get("http://www.example.com/form.html");
      my @forms = HTML::Form->parse($response->decoded_content,
  	base => $response->base,
  	charset => $response->content_charset,
      );

  In fact, the parse() method can parse from an C<HTTP::Response> object
  directly, so the example above can be more conveniently written as:

      my $ua = LWP::UserAgent->new;
      my $response = $ua->get("http://www.example.com/form.html");
      my @forms = HTML::Form->parse($response);

  Note that any object that implements a decoded_content(), base() and
  content_charset() method with similar behaviour as C<HTTP::Response> will do.

  Additional options might be passed in to control how the parse method
  behaves.  The following are all the options currently recognized:

  =over

  =item C<< base => $uri >>

  This is the URI used to retrive the original document.  This option is not optional ;-)

  =item C<< charset => $str >>

  Specify what charset the original document was encoded in.  This is used as
  the default for accept_charset.  If not provided this defaults to "UTF-8".

  =item C<< verbose => $bool >>

  Warn (print messages to STDERR) about any bad HTML form constructs found.
  You can trap these with $SIG{__WARN__}.

  =item C<< strict => $bool >>

  Initialize any form objects with the given strict attribute.

  =back


pkgId: d6798ead206f9e242ced95bc8ac523bcc97ec971a209d77141fecfe811b88416
name: local-perl-HTML-HTMLDoc
arch: noarch
version: 0.10
epoch: 0
release: 1
summary: HTML-HTMLDoc - Perl interface to the htmldoc program for producing PDF-Files from HTML-Content
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Michael Frankl <mfrankl@seibert-media.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTML-HTMLDoc-0.10-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTML-HTMLDoc-0.10-1.noarch.rpm
checksum_type: sha256
description:
  This Module provides an OO-interface to the htmldoc programm. To install this module you
  have to install the htmldoc program first. You can get it from http://www.htmldoc.org .

  You can use it to produce PDF or PS files from a HTML-document. Currently many but not all
  parameters of HTMLDoc are supported.

  You need to have HTMLDoc installed before installing this module.

  All the pdf-Methods return true for success or false for failure. You can test if errors
  occurred by calling the error-method.

  Normaly this module uses IPC::Open3 for communacation with the HTMLDOC process. However,
  in mod_perl-environments there appear problems with this module because the standard-output can not
  be captured. For this problem this module provides a fix doing the communication in file-mode.

  For this you can specify the parameter mode in the constructor:
  my $htmldoc = new HTMLDoc('mode'=>'file', 'tmpdir'=>'/tmp');


pkgId: d5ec7d2073fa2fcb81ef4569d70eab7d26a6a2069fa709fececf11730a246c6b
name: local-perl-HTML-Parser
arch: x86_64
version: 3.68
epoch: 0
release: 1
summary: HTML-Parser - HTML parser class
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTML-Parser-3.68-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTML-Parser-3.68-1.x86_64.rpm
checksum_type: sha256
description:
  Objects of the C<HTML::Parser> class will recognize markup and
  separate it from plain text (alias data content) in HTML
  documents.  As different kinds of markup and text are recognized, the
  corresponding event handlers are invoked.

  C<HTML::Parser> is not a generic SGML parser.  We have tried to
  make it able to deal with the HTML that is actually "out there", and
  it normally parses as closely as possible to the way the popular web
  browsers do it instead of strictly following one of the many HTML
  specifications from W3C.  Where there is disagreement, there is often
  an option that you can enable to get the official behaviour.

  The document to be parsed may be supplied in arbitrary chunks.  This
  makes on-the-fly parsing as documents are received from the network
  possible.

  If event driven parsing does not feel right for your application, you
  might want to use C<HTML::PullParser>.  This is an C<HTML::Parser>
  subclass that allows a more conventional program structure.


pkgId: f047b879530ed46020174aa3cdfede48b8cc8ea75432af5d4e4e33398e8c35ec
name: local-perl-HTML-Strip
arch: x86_64
version: 1.06
epoch: 0
release: 1
summary: HTML-Strip - Perl extension for stripping HTML markup from text.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Alex Bowley <kilinrax@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTML-Strip-1.06-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTML-Strip-1.06-1.x86_64.rpm
checksum_type: sha256
description:
  This module simply strips HTML-like markup from text in a very quick
  and brutal manner. It could quite easily be used to strip XML or SGML
  from text as well; but removing HTML markup is a much more common
  problem, hence this module lives in the HTML:: namespace.

  It is written in XS, and thus about five times quicker than using
  regular expressions for the same task.

  It does I<not> do any syntax checking (if you want that, use
  L<HTML::Parser>), instead it merely applies the following rules:

  =over 4

  =item 1

  Anything that looks like a tag, or group of tags will be replaced with
  a single space character. Tags are considered to be anything that
  starts with a C<E<lt>> and ends with a C<E<gt>>; with the caveat that a
  C<E<gt>> character may appear in either of the following without
  ending the tag:

  =over 4

  =item Quote

  Quotes are considered to start with either a C<'> or a C<"> character,
  and end with a matching character I<not> preceded by an even number or
  escaping slashes (i.e. C<\"> does not end the quote but C<\\\\"> does).

  =item Comment

  If the tag starts with an exclamation mark, it is assumed to be a
  declaration or a comment. Within such tags, C<E<gt>> characters do not
  end the tag if they appear within pairs of double dashes (e.g. C<E<lt>!--
  E<lt>a href="old.htm"E<gt>old pageE<lt>/aE<gt> --E<gt>> would be
  stripped completely).

  =back

  =item 2

  Anything the appears within so-called I<strip tags> is stripped as
  well. By default, these tags are C<title>, C<script>, C<style> and
  C<applet>.

  =back

  HTML::Strip maintains state between calls, so you can parse a document
  in chunks should you wish. If one chunk ends half-way through a tag,
  quote, comment, or whatever; it will remember this, and expect the
  next call to parse to start with the remains of said tag.

  If this is not going to be the case, be sure to call $hs->eof()
  between calls to $hs->parse().


pkgId: d4ee14816cc9489b50a2cd807540d0a0de2bd851c4caed839eeab5acb37a3261
name: local-perl-HTML-Tagset
arch: noarch
version: 3.20
epoch: 0
release: 1
summary: HTML-Tagset - data tables useful in parsing HTML
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Lester <andy@petdance.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTML-Tagset-3.20-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTML-Tagset-3.20-1.noarch.rpm
checksum_type: sha256
description:
  This module contains several data tables useful in various kinds of
  HTML parsing operations.

  Note that all tag names used are lowercase.

  In the following documentation, a "hashset" is a hash being used as a
  set -- the hash conveys that its keys are there, and the actual values
  associated with the keys are not significant.  (But what values are
  there, are always true.)


pkgId: d802b2ba2c6a95a85de7169079414b2653505e4702ae84a302fb56e2d8126318
name: local-perl-HTTP-Body
arch: noarch
version: 1.15
epoch: 0
release: 1
summary: HTTP-Body - HTTP Body Parser
description: None.
url: http://www.cpan.org
rpm_license: Artistic
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTTP-Body-1.15-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTTP-Body-1.15-1.noarch.rpm
checksum_type: sha256
rpm_vendor:
  Christian Hansen, C<chansen@cpan.org>, Sebastian Riedel, C<sri@cpan.org>, Andy Grundman, C<andy@hybridized.org>, Torsten Raudssus, C<getty@cpan.org>


pkgId: 2f311b0d5384d76f5e8d4408fdc6b28ff4bbbc9ae1d7cca3fe1cd9961183b64c
name: local-perl-HTTP-Cookies
arch: noarch
version: 6.00
epoch: 0
release: 1
summary: HTTP-Cookies - HTTP cookie jars
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTTP-Cookies-6.00-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTTP-Cookies-6.00-1.noarch.rpm
checksum_type: sha256
description:
  This class is for objects that represent a "cookie jar" -- that is, a
  database of all the HTTP cookies that a given LWP::UserAgent object
  knows about.

  Cookies are a general mechanism which server side connections can use
  to both store and retrieve information on the client side of the
  connection.  For more information about cookies refer to
  <URL:http://curl.haxx.se/rfc/cookie_spec.html> and
  <URL:http://www.cookiecentral.com/>.  This module also implements the
  new style cookies described in I<RFC 2965>.
  The two variants of cookies are supposed to be able to coexist happily.

  Instances of the class I<HTTP::Cookies> are able to store a collection
  of Set-Cookie2: and Set-Cookie: headers and are able to use this
  information to initialize Cookie-headers in I<HTTP::Request> objects.
  The state of a I<HTTP::Cookies> object can be saved in and restored from
  files.


pkgId: e22b668a3a8bdd4da51ad7548892521dd52715980f6b6479393e962fa3db4e06
name: local-perl-HTTP-Daemon
arch: noarch
version: 6.00
epoch: 0
release: 1
summary: HTTP-Daemon - a simple http server class
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTTP-Daemon-6.00-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTTP-Daemon-6.00-1.noarch.rpm
checksum_type: sha256
description:
  Instances of the C<HTTP::Daemon> class are HTTP/1.1 servers that
  listen on a socket for incoming requests. The C<HTTP::Daemon> is a
  subclass of C<IO::Socket::INET>, so you can perform socket operations
  directly on it too.

  The accept() method will return when a connection from a client is
  available.  The returned value will be an C<HTTP::Daemon::ClientConn>
  object which is another C<IO::Socket::INET> subclass.  Calling the
  get_request() method on this object will read data from the client and
  return an C<HTTP::Request> object.  The ClientConn object also provide
  methods to send back various responses.

  This HTTP daemon does not fork(2) for you.  Your application, i.e. the
  user of the C<HTTP::Daemon> is responsible for forking if that is
  desirable.  Also note that the user is responsible for generating
  responses that conform to the HTTP/1.1 protocol.

  The following methods of C<HTTP::Daemon> are new (or enhanced) relative
  to the C<IO::Socket::INET> base class:

  =over 4

  =item $d = HTTP::Daemon->new

  =item $d = HTTP::Daemon->new( %opts )

  The constructor method takes the same arguments as the
  C<IO::Socket::INET> constructor, but unlike its base class it can also
  be called without any arguments.  The daemon will then set up a listen
  queue of 5 connections and allocate some random port number.

  A server that wants to bind to some specific address on the standard
  HTTP port will be constructed like this:

    $d = HTTP::Daemon->new(
             LocalAddr => 'www.thisplace.com',
             LocalPort => 80,
         );

  See L<IO::Socket::INET> for a description of other arguments that can
  be used configure the daemon during construction.

  =item $c = $d->accept

  =item $c = $d->accept( $pkg )

  =item ($c, $peer_addr) = $d->accept

  This method works the same the one provided by the base class, but it
  returns an C<HTTP::Daemon::ClientConn> reference by default.  If a
  package name is provided as argument, then the returned object will be
  blessed into the given class.  It is probably a good idea to make that
  class a subclass of C<HTTP::Daemon::ClientConn>.

  The accept method will return C<undef> if timeouts have been enabled
  and no connection is made within the given time.  The timeout() method
  is described in L<IO::Socket>.

  In list context both the client object and the peer address will be
  returned; see the description of the accept method L<IO::Socket> for
  details.

  =item $d->url

  Returns a URL string that can be used to access the server root.

  =item $d->product_tokens

  Returns the name that this server will use to identify itself.  This
  is the string that is sent with the C<Server> response header.  The
  main reason to have this method is that subclasses can override it if
  they want to use another product name.

  The default is the string "libwww-perl-daemon/#.##" where "#.##" is
  replaced with the version number of this module.

  =back

  The C<HTTP::Daemon::ClientConn> is a C<IO::Socket::INET>
  subclass. Instances of this class are returned by the accept() method
  of C<HTTP::Daemon>.  The following methods are provided:

  =over 4

  =item $c->get_request

  =item $c->get_request( $headers_only )

  This method reads data from the client and turns it into an
  C<HTTP::Request> object which is returned.  It returns C<undef>
  if reading fails.  If it fails, then the C<HTTP::Daemon::ClientConn>
  object ($c) should be discarded, and you should not try call this
  method again on it.  The $c->reason method might give you some
  information about why $c->get_request failed.

  The get_request() method will normally not return until the whole
  request has been received from the client.  This might not be what you
  want if the request is an upload of a large file (and with chunked
  transfer encoding HTTP can even support infinite request messages -
  uploading live audio for instance).  If you pass a TRUE value as the
  $headers_only argument, then get_request() will return immediately
  after parsing the request headers and you are responsible for reading
  the rest of the request content.  If you are going to call
  $c->get_request again on the same connection you better read the
  correct number of bytes.

  =item $c->read_buffer

  =item $c->read_buffer( $new_value )

  Bytes read by $c->get_request, but not used are placed in the I<read
  buffer>.  The next time $c->get_request is called it will consume the
  bytes in this buffer before reading more data from the network
  connection itself.  The read buffer is invalid after $c->get_request
  has failed.

  If you handle the reading of the request content yourself you need to
  empty this buffer before you read more and you need to place
  unconsumed bytes here.  You also need this buffer if you implement
  services like I<101 Switching Protocols>.

  This method always returns the old buffer content and can optionally
  replace the buffer content if you pass it an argument.

  =item $c->reason

  When $c->get_request returns C<undef> you can obtain a short string
  describing why it happened by calling $c->reason.

  =item $c->proto_ge( $proto )

  Return TRUE if the client announced a protocol with version number
  greater or equal to the given argument.  The $proto argument can be a
  string like "HTTP/1.1" or just "1.1".

  =item $c->antique_client

  Return TRUE if the client speaks the HTTP/0.9 protocol.  No status
  code and no headers should be returned to such a client.  This should
  be the same as !$c->proto_ge("HTTP/1.0").

  =item $c->head_request

  Return TRUE if the last request was a C<HEAD> request.  No content
  body must be generated for these requests.

  =item $c->force_last_request

  Make sure that $c->get_request will not try to read more requests off
  this connection.  If you generate a response that is not self
  delimiting, then you should signal this fact by calling this method.

  This attribute is turned on automatically if the client announces
  protocol HTTP/1.0 or worse and does not include a "Connection:
  Keep-Alive" header.  It is also turned on automatically when HTTP/1.1
  or better clients send the "Connection: close" request header.

  =item $c->send_status_line

  =item $c->send_status_line( $code )

  =item $c->send_status_line( $code, $mess )

  =item $c->send_status_line( $code, $mess, $proto )

  Send the status line back to the client.  If $code is omitted 200 is
  assumed.  If $mess is omitted, then a message corresponding to $code
  is inserted.  If $proto is missing the content of the
  $HTTP::Daemon::PROTO variable is used.

  =item $c->send_crlf

  Send the CRLF sequence to the client.

  =item $c->send_basic_header

  =item $c->send_basic_header( $code )

  =item $c->send_basic_header( $code, $mess )

  =item $c->send_basic_header( $code, $mess, $proto )

  Send the status line and the "Date:" and "Server:" headers back to
  the client.  This header is assumed to be continued and does not end
  with an empty CRLF line.

  See the description of send_status_line() for the description of the
  accepted arguments.

  =item $c->send_header( $field, $value )

  =item $c->send_header( $field1, $value1, $field2, $value2, ... )

  Send one or more header lines.

  =item $c->send_response( $res )

  Write a C<HTTP::Response> object to the
  client as a response.  We try hard to make sure that the response is
  self delimiting so that the connection can stay persistent for further
  request/response exchanges.

  The content attribute of the C<HTTP::Response> object can be a normal
  string or a subroutine reference.  If it is a subroutine, then
  whatever this callback routine returns is written back to the
  client as the response content.  The routine will be called until it
  return an undefined or empty value.  If the client is HTTP/1.1 aware
  then we will use chunked transfer encoding for the response.

  =item $c->send_redirect( $loc )

  =item $c->send_redirect( $loc, $code )

  =item $c->send_redirect( $loc, $code, $entity_body )

  Send a redirect response back to the client.  The location ($loc) can
  be an absolute or relative URL. The $code must be one the redirect
  status codes, and defaults to "301 Moved Permanently"

  =item $c->send_error

  =item $c->send_error( $code )

  =item $c->send_error( $code, $error_message )

  Send an error response back to the client.  If the $code is missing a
  "Bad Request" error is reported.  The $error_message is a string that
  is incorporated in the body of the HTML entity body.

  =item $c->send_file_response( $filename )

  Send back a response with the specified $filename as content.  If the
  file is a directory we try to generate an HTML index of it.

  =item $c->send_file( $filename )

  =item $c->send_file( $fd )

  Copy the file to the client.  The file can be a string (which
  will be interpreted as a filename) or a reference to an C<IO::Handle>
  or glob.

  =item $c->daemon

  Return a reference to the corresponding C<HTTP::Daemon> object.

  =back


pkgId: ecf6a8e4773003f21a12af7ca3edc3942b70f124e2604443eb660faaba96e77a
name: local-perl-HTTP-Date
arch: noarch
version: 6.00
epoch: 0
release: 1
summary: HTTP-Date - date conversion routines
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTTP-Date-6.00-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTTP-Date-6.00-1.noarch.rpm
checksum_type: sha256
description:
  This module provides functions that deal the date formats used by the
  HTTP protocol (and then some more).  Only the first two functions,
  time2str() and str2time(), are exported by default.

  =over 4

  =item time2str( [$time] )

  The time2str() function converts a machine time (seconds since epoch)
  to a string.  If the function is called without an argument or with an
  undefined argument, it will use the current time.

  The string returned is in the format preferred for the HTTP protocol.
  This is a fixed length subset of the format defined by RFC 1123,
  represented in Universal Time (GMT).  An example of a time stamp
  in this format is:

     Sun, 06 Nov 1994 08:49:37 GMT

  =item str2time( $str [, $zone] )

  The str2time() function converts a string to machine time.  It returns
  C<undef> if the format of $str is unrecognized, otherwise whatever the
  C<Time::Local> functions can make out of the parsed time.  Dates
  before the system's epoch may not work on all operating systems.  The
  time formats recognized are the same as for parse_date().

  The function also takes an optional second argument that specifies the
  default time zone to use when converting the date.  This parameter is
  ignored if the zone is found in the date string itself.  If this
  parameter is missing, and the date string format does not contain any
  zone specification, then the local time zone is assumed.

  If the zone is not "C<GMT>" or numerical (like "C<-0800>" or
  "C<+0100>"), then the C<Time::Zone> module must be installed in order
  to get the date recognized.

  =item parse_date( $str )

  This function will try to parse a date string, and then return it as a
  list of numerical values followed by a (possible undefined) time zone
  specifier; ($year, $month, $day, $hour, $min, $sec, $tz).  The $year
  returned will B<not> have the number 1900 subtracted from it and the
  $month numbers start with 1.

  In scalar context the numbers are interpolated in a string of the
  "YYYY-MM-DD hh:mm:ss TZ"-format and returned.

  If the date is unrecognized, then the empty list is returned.

  The function is able to parse the following formats:

   "Wed, 09 Feb 1994 22:23:32 GMT"       -- HTTP format
   "Thu Feb  3 17:03:55 GMT 1994"        -- ctime(3) format
   "Thu Feb  3 00:00:00 1994",           -- ANSI C asctime() format
   "Tuesday, 08-Feb-94 14:15:29 GMT"     -- old rfc850 HTTP format
   "Tuesday, 08-Feb-1994 14:15:29 GMT"   -- broken rfc850 HTTP format

   "03/Feb/1994:17:03:55 -0700"   -- common logfile format
   "09 Feb 1994 22:23:32 GMT"     -- HTTP format (no weekday)
   "08-Feb-94 14:15:29 GMT"       -- rfc850 format (no weekday)
   "08-Feb-1994 14:15:29 GMT"     -- broken rfc850 format (no weekday)

   "1994-02-03 14:15:29 -0100"    -- ISO 8601 format
   "1994-02-03 14:15:29"          -- zone is optional
   "1994-02-03"                   -- only date
   "1994-02-03T14:15:29"          -- Use T as separator
   "19940203T141529Z"             -- ISO 8601 compact format
   "19940203"                     -- only date

   "08-Feb-94"         -- old rfc850 HTTP format    (no weekday, no time)
   "08-Feb-1994"       -- broken rfc850 HTTP format (no weekday, no time)
   "09 Feb 1994"       -- proposed new HTTP format  (no weekday, no time)
   "03/Feb/1994"       -- common logfile format     (no time, no offset)

   "Feb  3  1994"      -- Unix 'ls -l' format
   "Feb  3 17:03"      -- Unix 'ls -l' format

   "11-15-96  03:52PM" -- Windows 'dir' format

  The parser ignores leading and trailing whitespace.  It also allow the
  seconds to be missing and the month to be numerical in most formats.

  If the year is missing, then we assume that the date is the first
  matching date I<before> current month.  If the year is given with only
  2 digits, then parse_date() will select the century that makes the
  year closest to the current date.

  =item time2iso( [$time] )

  Same as time2str(), but returns a "YYYY-MM-DD hh:mm:ss"-formatted
  string representing time in the local time zone.

  =item time2isoz( [$time] )

  Same as time2str(), but returns a "YYYY-MM-DD hh:mm:ssZ"-formatted
  string representing Universal Time.


  =back


pkgId: 4bbecdc384a827748322f26f2b7ca48f5ca5f33ce304613e2dc29009703fa9ba
name: local-perl-HTTP-Message
arch: noarch
version: 6.02
epoch: 0
release: 1
summary: HTTP-Message - HTTP style messages
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTTP-Message-6.02-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTTP-Message-6.02-1.noarch.rpm
checksum_type: sha256
description:
  An C<HTTP::Message> object contains some headers and a content body.
  The following methods are available:

  =over 4

  =item $mess = HTTP::Message->new

  =item $mess = HTTP::Message->new( $headers )

  =item $mess = HTTP::Message->new( $headers, $content )

  This constructs a new message object.  Normally you would want
  construct C<HTTP::Request> or C<HTTP::Response> objects instead.

  The optional $header argument should be a reference to an
  C<HTTP::Headers> object or a plain array reference of key/value pairs.
  If an C<HTTP::Headers> object is provided then a copy of it will be
  embedded into the constructed message, i.e. it will not be owned and
  can be modified afterwards without affecting the message.

  The optional $content argument should be a string of bytes.

  =item $mess = HTTP::Message->parse( $str )

  This constructs a new message object by parsing the given string.

  =item $mess->headers

  Returns the embedded C<HTTP::Headers> object.

  =item $mess->headers_as_string

  =item $mess->headers_as_string( $eol )

  Call the as_string() method for the headers in the
  message.  This will be the same as

      $mess->headers->as_string

  but it will make your program a whole character shorter :-)

  =item $mess->content

  =item $mess->content( $bytes )

  The content() method sets the raw content if an argument is given.  If no
  argument is given the content is not touched.  In either case the
  original raw content is returned.

  Note that the content should be a string of bytes.  Strings in perl
  can contain characters outside the range of a byte.  The C<Encode>
  module can be used to turn such strings into a string of bytes.

  =item $mess->add_content( $bytes )

  The add_content() methods appends more data bytes to the end of the
  current content buffer.

  =item $mess->add_content_utf8( $string )

  The add_content_utf8() method appends the UTF-8 bytes representing the
  string to the end of the current content buffer.

  =item $mess->content_ref

  =item $mess->content_ref( \$bytes )

  The content_ref() method will return a reference to content buffer string.
  It can be more efficient to access the content this way if the content
  is huge, and it can even be used for direct manipulation of the content,
  for instance:

    ${$res->content_ref} =~ s/\bfoo\b/bar/g;

  This example would modify the content buffer in-place.

  If an argument is passed it will setup the content to reference some
  external source.  The content() and add_content() methods
  will automatically dereference scalar references passed this way.  For
  other references content() will return the reference itself and
  add_content() will refuse to do anything.

  =item $mess->content_charset

  This returns the charset used by the content in the message.  The
  charset is either found as the charset attribute of the
  C<Content-Type> header or by guessing.

  See L<http://www.w3.org/TR/REC-html40/charset.html#spec-char-encoding>
  for details about how charset is determined.

  =item $mess->decoded_content( %options )

  Returns the content with any C<Content-Encoding> undone and for textual content
  the raw content encoded to Perl's Unicode strings.  If the C<Content-Encoding>
  or C<charset> of the message is unknown this method will fail by returning
  C<undef>.

  The following options can be specified.

  =over

  =item C<charset>

  This override the charset parameter for text content.  The value
  C<none> can used to suppress decoding of the charset.

  =item C<default_charset>

  This override the default charset guessed by content_charset() or
  if that fails "ISO-8859-1".

  =item C<alt_charset>

  If decoding fails because the charset specified in the Content-Type header
  isn't recognized by Perl's Encode module, then try decoding using this charset
  instead of failing.  The C<alt_charset> might be specified as C<none> to simply
  return the string without any decoding of charset as alternative.

  =item C<charset_strict>

  Abort decoding if malformed characters is found in the content.  By
  default you get the substitution character ("\x{FFFD}") in place of
  malformed characters.

  =item C<raise_error>

  If TRUE then raise an exception if not able to decode content.  Reason
  might be that the specified C<Content-Encoding> or C<charset> is not
  supported.  If this option is FALSE, then decoded_content() will return
  C<undef> on errors, but will still set $@.

  =item C<ref>

  If TRUE then a reference to decoded content is returned.  This might
  be more efficient in cases where the decoded content is identical to
  the raw content as no data copying is required in this case.

  =back

  =item $mess->decodable

  =item HTTP::Message::decodable()

  This returns the encoding identifiers that decoded_content() can
  process.  In scalar context returns a comma separated string of
  identifiers.

  This value is suitable for initializing the C<Accept-Encoding> request
  header field.

  =item $mess->decode

  This method tries to replace the content of the message with the
  decoded version and removes the C<Content-Encoding> header.  Returns
  TRUE if successful and FALSE if not.

  If the message does not have a C<Content-Encoding> header this method
  does nothing and returns TRUE.

  Note that the content of the message is still bytes after this method
  has been called and you still need to call decoded_content() if you
  want to process its content as a string.

  =item $mess->encode( $encoding, ... )

  Apply the given encodings to the content of the message.  Returns TRUE
  if successful. The "identity" (non-)encoding is always supported; other
  currently supported encodings, subject to availability of required
  additional modules, are "gzip", "deflate", "x-bzip2" and "base64".

  A successful call to this function will set the C<Content-Encoding>
  header.

  Note that C<multipart/*> or C<message/*> messages can't be encoded and
  this method will croak if you try.

  =item $mess->parts

  =item $mess->parts( @parts )

  =item $mess->parts( \@parts )

  Messages can be composite, i.e. contain other messages.  The composite
  messages have a content type of C<multipart/*> or C<message/*>.  This
  method give access to the contained messages.

  The argumentless form will return a list of C<HTTP::Message> objects.
  If the content type of $msg is not C<multipart/*> or C<message/*> then
  this will return the empty list.  In scalar context only the first
  object is returned.  The returned message parts should be regarded as
  read-only (future versions of this library might make it possible
  to modify the parent by modifying the parts).

  If the content type of $msg is C<message/*> then there will only be
  one part returned.

  If the content type is C<message/http>, then the return value will be
  either an C<HTTP::Request> or an C<HTTP::Response> object.

  If an @parts argument is given, then the content of the message will be
  modified. The array reference form is provided so that an empty list
  can be provided.  The @parts array should contain C<HTTP::Message>
  objects.  The @parts objects are owned by $mess after this call and
  should not be modified or made part of other messages.

  When updating the message with this method and the old content type of
  $mess is not C<multipart/*> or C<message/*>, then the content type is
  set to C<multipart/mixed> and all other content headers are cleared.

  This method will croak if the content type is C<message/*> and more
  than one part is provided.

  =item $mess->add_part( $part )

  This will add a part to a message.  The $part argument should be
  another C<HTTP::Message> object.  If the previous content type of
  $mess is not C<multipart/*> then the old content (together with all
  content headers) will be made part #1 and the content type made
  C<multipart/mixed> before the new part is added.  The $part object is
  owned by $mess after this call and should not be modified or made part
  of other messages.

  There is no return value.

  =item $mess->clear

  Will clear the headers and set the content to the empty string.  There
  is no return value

  =item $mess->protocol

  =item $mess->protocol( $proto )

  Sets the HTTP protocol used for the message.  The protocol() is a string
  like C<HTTP/1.0> or C<HTTP/1.1>.

  =item $mess->clone

  Returns a copy of the message object.

  =item $mess->as_string

  =item $mess->as_string( $eol )

  Returns the message formatted as a single string.

  The optional $eol parameter specifies the line ending sequence to use.
  The default is "\n".  If no $eol is given then as_string will ensure
  that the returned string is newline terminated (even when the message
  content is not).  No extra newline is appended if an explicit $eol is
  passed.

  =item $mess->dump( %opt )

  Returns the message formatted as a string.  In void context print the string.

  This differs from C<< $mess->as_string >> in that it escapes the bytes
  of the content so that it's safe to print them and it limits how much
  content to print.  The escapes syntax used is the same as for Perl's
  double quoted strings.  If there is no content the string "(no
  content)" is shown in its place.

  Options to influence the output can be passed as key/value pairs. The
  following options are recognized:

  =over

  =item maxlength => $num

  How much of the content to show.  The default is 512.  Set this to 0
  for unlimited.

  If the content is longer then the string is chopped at the limit and
  the string "...\n(### more bytes not shown)" appended.

  =item prefix => $str

  A string that will be prefixed to each line of the dump.

  =back

  =back

  All methods unknown to C<HTTP::Message> itself are delegated to the
  C<HTTP::Headers> object that is part of every message.  This allows
  convenient access to these methods.  Refer to L<HTTP::Headers> for
  details of these methods:

      $mess->header( $field => $val )
      $mess->push_header( $field => $val )
      $mess->init_header( $field => $val )
      $mess->remove_header( $field )
      $mess->remove_content_headers
      $mess->header_field_names
      $mess->scan( \&doit )

      $mess->date
      $mess->expires
      $mess->if_modified_since
      $mess->if_unmodified_since
      $mess->last_modified
      $mess->content_type
      $mess->content_encoding
      $mess->content_length
      $mess->content_language
      $mess->title
      $mess->user_agent
      $mess->server
      $mess->from
      $mess->referer
      $mess->www_authenticate
      $mess->authorization
      $mess->proxy_authorization
      $mess->authorization_basic
      $mess->proxy_authorization_basic


pkgId: 429ff5afb783418c9fd52d3a97eea818cc95224f05a86bcb06fdc927b3b47234
name: local-perl-HTTP-Negotiate
arch: noarch
version: 6.00
epoch: 0
release: 1
summary: HTTP-Negotiate - choose a variant to serve
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTTP-Negotiate-6.00-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTTP-Negotiate-6.00-1.noarch.rpm
checksum_type: sha256
description:
  This module provides a complete implementation of the HTTP content
  negotiation algorithm specified in F<draft-ietf-http-v11-spec-00.ps>
  chapter 12.  Content negotiation allows for the selection of a
  preferred content representation based upon attributes of the
  negotiable variants and the value of the various Accept* header fields
  in the request.

  The variants are ordered by preference by calling the function
  choose().

  The first parameter is reference to an array of the variants to
  choose among.
  Each element in this array is an array with the values [$id, $qs,
  $content_type, $content_encoding, $charset, $content_language,
  $content_length] whose meanings are described
  below. The $content_encoding and $content_language can be either a
  single scalar value or an array reference if there are several values.

  The second optional parameter is either a HTTP::Headers or a HTTP::Request
  object which is searched for "Accept*" headers.  If this
  parameter is missing, then the accept specification is initialized
  from the CGI environment variables HTTP_ACCEPT, HTTP_ACCEPT_CHARSET,
  HTTP_ACCEPT_ENCODING and HTTP_ACCEPT_LANGUAGE.

  In an array context, choose() returns a list of [variant
  identifier, calculated quality, size] tuples.  The values are sorted by
  quality, highest quality first.  If the calculated quality is the same
  for two variants, then they are sorted by size (smallest first). I<E.g.>:

    (['var1', 1, 2000], ['var2', 0.3, 512], ['var3', 0.3, 1024]);

  Note that also zero quality variants are included in the return list
  even if these should never be served to the client.

  In a scalar context, it returns the identifier of the variant with the
  highest score or C<undef> if none have non-zero quality.

  If the $HTTP::Negotiate::DEBUG variable is set to TRUE, then a lot of
  noise is generated on STDOUT during evaluation of choose().


pkgId: e3431116cf5b5ea367381c56a2894bc3788e2d1783037f0841adb4396928c321
name: local-perl-HTTP-Server-Simple
arch: noarch
version: 0.44
epoch: 0
release: 1
summary: HTTP-Server-Simple - Lightweight HTTP server
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jesse Vincent <jesse@bestpractical.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTTP-Server-Simple-0.44-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTTP-Server-Simple-0.44-1.noarch.rpm
checksum_type: sha256
description:
  This is a simple standalone HTTP server. By default, it doesn't thread
  or fork. It does, however, act as a simple frontend which can be used
  to build a standalone web-based application or turn a CGI into one.

  It is possible to use L<Net::Server> classes to create forking,
  pre-forking, and other types of more complicated servers; see
  L</net_server>.

  By default, the server traps a few signals:

  =over

  =item HUP

  When you C<kill -HUP> the server, it lets the current request finish being
  processed, then uses the C<restart> method to re-exec itself. Please note that
  in order to provide restart-on-SIGHUP, HTTP::Server::Simple sets a SIGHUP
  handler during initialisation. If your request handling code forks you need to
  make sure you reset this or unexpected things will happen if somebody sends a
  HUP to all running processes spawned by your app (e.g. by "kill -HUP <script>")

  =item PIPE

  If the server detects a broken pipe while writing output to the client,
  it ignores the signal. Otherwise, a client closing the connection early
  could kill the server.

  =back


pkgId: a642642c6eb2685c700e1368f8caff55e86770caad11df8f082ca8052729562a
name: local-perl-HTTP-Server-Simple-PSGI
arch: noarch
version: 0.14
epoch: 0
release: 1
summary: HTTP-Server-Simple-PSGI - PSGI handler for HTTP::Server::Simple
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tokuhiro MatsunoKazuhiro <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-HTTP-Server-Simple-PSGI-0.14-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-HTTP-Server-Simple-PSGI-0.14-1.noarch.rpm
checksum_type: sha256
description:
  HTTP::Server::Simple::PSGI is a HTTP::Server::Simple based HTTP server
  that can run PSGI applications. This module only depends on
  L<HTTP::Server::Simple>, which itself doesn't depend on any non-core
  modules so it's best to be used as an embedded web server.


pkgId: b1ebae932a32daa92ec0967188842ba7878f471c2aba2ce5d72d41c0315dfcad
name: local-perl-Hash-MultiValue
arch: noarch
version: 0.10
epoch: 0
release: 1
summary: Hash-MultiValue - Store multiple values per key
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tatsuhiko Miyagawa <miyagawa@bulknews.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Hash-MultiValue-0.10-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Hash-MultiValue-0.10-1.noarch.rpm
checksum_type: sha256
description:
  Hash::MultiValue is an object (and a plain hash reference) that may
  contain multiple values per key, inspired by MultiDict of WebOb.


pkgId: 02856593b890da0682b61f5707f48c7cc6038eb0bf1bc6ac6385a24384e3be2c
name: local-perl-IO-Compress
arch: x86_64
version: 2.033
epoch: 0
release: 162.ep
summary: IO::Compress wrapper for modules
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-IO-Compress-2.033-162.ep.x86_64.rpm
checksum_type: sha256
description:
  This module is the base class for all IO::Compress and IO::Uncompress modules.
  This module is not intended for direct use in application code. Its sole
  purpose is to to be sub-classed by IO::Compress modules.


pkgId: cf29d7308cc2697b382fd1a301cc307c3a8786e6929f37c0dbc6d61c6a784a2a
name: local-perl-IO-Compress
arch: noarch
version: 2.037
epoch: 0
release: 1
summary: IO-Compress - IO Interface to compressed data files/buffers
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Paul Marquess <pmqs@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-IO-Compress-2.037-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-IO-Compress-2.037-1.noarch.rpm
checksum_type: sha256
description:
  This module is not intended for direct use in application code. Its sole
  purpose if to to be sub-classed by IO::Compress modules.


pkgId: 6f479877f71af7196bf77ce9f9b3bb7f4512386682aa06fa7191d79fc3fe0466
name: local-perl-IO-Interface
arch: x86_64
version: 1.06
epoch: 0
release: 1
summary: IO-Interface - Perl extension for access to network card configuration information
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Lincoln Stein <Eltlstein@cshl.orgEgt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-IO-Interface-1.06-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-IO-Interface-1.06-1.x86_64.rpm
checksum_type: sha256
description:
  IO::Interface adds methods to IO::Socket objects that allows them to
  be used to retrieve and change information about the network
  interfaces on your system.  In addition to the object-oriented access
  methods, you can use a function-oriented style.

  THIS API IS DEPRECATED. Please see L<IO::Interface::Simple> for the
  preferred way to get and set interface configuration information.


pkgId: d9898647bbd95a9e29147318c2782c710499a02ed5d35704867fd4585e0e0d62
name: local-perl-IO-LockedFile
arch: noarch
version: 0.23
epoch: 0
release: 1
summary: IO-LockedFile - supply object methods for locking files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Rani Pinchuk <rani@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-IO-LockedFile-0.23-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-IO-LockedFile-0.23-1.noarch.rpm
checksum_type: sha256
description:
  In its simplistic use, the B<IO::LockedFile> class gives us the same
  interface of the B<IO::File> class with the unique difference that the
  files we deal with are locked using the B<Flock> mechanism (using the
  C<flock> function).

  If during the running of the process, it crashed - the file will
  be automatically unlocked. Actually - if the B<IO::LockedFile> object goes
  out of scope, the file is automatically closed and unlocked.

  So, if you are just interested in having locked files with C<flock>, you
  can skip most of the documentation below.

  If, on the other hand, you are interested in locking files with other
  schemes then B<Flock>, or you want to control the behavior of the locking
  (having non blocking lock for example), read on.

  Actually the class B<IO::LockedFile> is kind of abstract class.

  Why abstract? Because methods of this class call the methods C<lock>
  and C<unlock>. But those methods are not really implemented in this class.
  They suppose to be implemented in the derived classes of B<IO::LockedFile>.

  Why "kind" of abstract? Because the constructor of this class will return an
  object!

  How abstract class can create objects? This is done by having the constructor
  returning object that is actually an object of one of the derived classes of
  B<IO::LockedFile>.

  So by default the constructor of B<IO::LockedFile> will return an object of
  B<IO::LockedFile::Flock>. For example, the following:

     use IO::LockedFile;
     $lock = new IO::LockedFile(">bla");
     print ref($lock);

  Will give:

     IO::LockedFile::Flock

  So what are the conclusions here?

  First of all - do not be surprised to get object of derived class from the
  constructor of B<IO::LockedFile>.

  Secondly - by changing the default behavior of the constructor of
  B<IO::LockedFile>, we can get object of other class which means that we
  have a locked file that is locked with other scheme.

  The default behavior of the constructor is determined by the global options.

  We can access this global options, or the options per object using the method
  C<set_option> and C<get_option>.

  We can set the global options in the use line:

    use IO::LockedFile 'Flock'; # set the default scheme to be Flock

    use IO::LockedFile ( scheme => Flock );

  We can also set the options of a new object by passing the options to the
  constructor, as we will see below. We can change the options of an existing
  object by using the C<set_option> method.

  Which options are available?

  =over 4

  =item I<scheme>

  The I<scheme> let us define which derived class we use for the object
  we create.
  See below which derived classes are available. The default scheme is 'Flock'.

  =item I<block>

  The I<block> option can be 1 or 0 (true or false). If it is 1, a call to the
  C<open> method or to the constructor will be blocked if the file we try to open
  is already locked. This means that those methods will not return till the
  file is unlocked. If the value of the I<block> option is 0, the C<open> and the
  constructor will return immediately in any case. If the file is locked,
  those methods will return undef. The default value of the I<block> option is
  1.

  =item I<lock>

  The I<lock> option can be 1 or 0 (true or false). It defines if the file we
  open when we create the object will be opened locked. Sometimes, we want
  to have a file that can be locked, yet we do not want to open it locked from
  the beginning. For example if we want to print into a log file, usually we
  want to lock that file only when we print into it. Yet, it might be that
  when we open the file in the beginning we do not print into it immediately.
  In that case we will prefer to open the file as unlocked, and later we will
  lock it when needed. The default value of the I<lock> option is 1.

  =back

  There might be extra options that are used by one of the derived classes. So
  according to the scheme you choose to use, please look in the manual page of
  the class that implement that scheme.

  Finally, some information that is connected to a certain scheme will be found
  in the classes that are derived from this class. For example, compatibility
  issues will be discussed in each derived classes.

  The classes that currently implement the interface that B<IO::LockedFile>
  defines are:

  =over 4

  =item *

  B<IO::LockedFile::Flock>

  =back


pkgId: 66a5f1ac86a2db7ab08dd285b0cafef45028228a07a9ae1e010bf9e43d9042f1
name: local-perl-IO-Socket-Multicast
arch: x86_64
version: 1.12
epoch: 0
release: 1
summary: IO-Socket-Multicast - Send and receive multicast messages
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Lincoln Stein <lstein@cshl.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-IO-Socket-Multicast-1.12-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-IO-Socket-Multicast-1.12-1.x86_64.rpm
checksum_type: sha256
description:
  The IO::Socket::Multicast module subclasses IO::Socket::INET to enable
  you to manipulate multicast groups.  With this module (and an
  operating system that supports multicasting), you will be able to
  receive incoming multicast transmissions and generate your own
  outgoing multicast packets.

  This module requires IO::Interface version 0.94 or higher.


pkgId: fa7422b804595e1bc4d0ab57f027dfd648d31b8d7a5769cc0480aeb61cccac1e
name: local-perl-IO-Socket-SSL
arch: noarch
version: 1.44
epoch: 0
release: 1
summary: IO-Socket-SSL - Nearly transparent SSL encapsulation for IO::Socket::INET.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Steffen Ullrich & Peter Behroozi & Marko Asplund
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-IO-Socket-SSL-1.44-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-IO-Socket-SSL-1.44-1.noarch.rpm
checksum_type: sha256
description:
  This module is a true drop-in replacement for IO::Socket::INET that uses
  SSL to encrypt data before it is transferred to a remote server or
  client.	 IO::Socket::SSL supports all the extra features that one needs
  to write a full-featured SSL client or server application: multiple SSL contexts,
  cipher selection, certificate verification, and SSL version selection.	As an
  extra bonus, it works perfectly with mod_perl.

  If you have never used SSL before, you should read the appendix labelled 'Using SSL'
  before attempting to use this module.

  If you have used this module before, read on, as versions 0.93 and above
  have several changes from the previous IO::Socket::SSL versions (especially
  see the note about return values).

  If you are using non-blocking sockets read on, as version 0.98 added better
  support for non-blocking.

  If you are trying to use it with threads see the BUGS section.


pkgId: ec33bfdb8c64bcc1f6c97c52b48b0434d99d327cea573316ed740d65d10317ee
name: local-perl-IO-Tty
arch: x86_64
version: 1.10
epoch: 0
release: 1
summary: IO-Tty - Pseudo ttys and constants
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Roland Giersig <RGiersig@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-IO-Tty-1.10-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-IO-Tty-1.10-1.x86_64.rpm
checksum_type: sha256
description:
  C<IO::Tty> is used internally by C<IO::Pty> to create a pseudo-tty.
  You wouldn't want to use it directly except to import constants, use
  C<IO::Pty>.  For a list of importable constants, see
  L<IO::Tty::Constant>.

  Windows is now supported, but ONLY under the Cygwin
  environment, see L<http://sources.redhat.com/cygwin/>.

  Please note that pty creation is very system-dependend.  From my
  experience, any modern POSIX system should be fine.  Find below a list
  of systems that C<IO::Tty> should work on.  A more detailed table
  (which is slowly getting out-of-date) is available from the project
  pages document manager at SourceForge
  L<http://sourceforge.net/projects/expectperl/>.

  If you have problems on your system and your system is listed in the
  "verified" list, you probably have some non-standard setup, e.g. you
  compiled your Linux-kernel yourself and disabled ptys (bummer!).
  Please ask your friendly sysadmin for help.

  If your system is not listed, unpack the latest version of C<IO::Tty>,
  do a C<'perl Makefile.PL; make; make test; uname -a'> and send me
  (F<RGiersig@cpan.org>) the results and I'll see what I can deduce from
  that.  There are chances that it will work right out-of-the-box...

  If it's working on your system, please send me a short note with
  details (version number, distribution, etc. 'uname -a' and 'perl -V'
  is a good start; also, the output from "perl Makefile.PL" contains a
  lot of interesting info, so please include that as well) so I can get
  an overview.  Thanks!


pkgId: 96e2825ae61054e85fa7112e9d7834d7eac88d1716c2e15e8f8e2c4e2de390d0
name: local-perl-IO-Zlib
arch: noarch
version: 1.10
epoch: 1
release: 162.ep
summary: Perl IO:: style interface to Compress::Zlib
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-IO-Zlib-1.10-162.ep.noarch.rpm
checksum_type: sha256
description:
  This modules provides an IO:: style interface to the Compress::Zlib package.
  The main advantage is that you can use an IO::Zlib object in much the same way
  as an IO::File object so you can have common code that doesn't know which sort
  of file it is using.


pkgId: c76d7799046f567c76868bcff2a4bb956067d7ef53f555c595cb026dab890878
name: local-perl-IO-stringy
arch: noarch
version: 2.110
epoch: 0
release: 1
summary: IO-stringy - stringy - I/O on in-core objects like strings and arrays
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-IO-stringy-2.110-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-IO-stringy-2.110-1.noarch.rpm
checksum_type: sha256
description:
  This toolkit primarily provides modules for performing both traditional
  and object-oriented i/o) on things I<other> than normal filehandles;
  in particular, L<IO::Scalar|IO::Scalar>, L<IO::ScalarArray|IO::ScalarArray>,
  and L<IO::Lines|IO::Lines>.

  In the more-traditional IO::Handle front, we
  have L<IO::AtomicFile|IO::AtomicFile>
  which may be used to painlessly create files which are updated
  atomically.

  And in the "this-may-prove-useful" corner, we have L<IO::Wrap|IO::Wrap>,
  whose exported wraphandle() function will clothe anything that's not
  a blessed object in an IO::Handle-like wrapper... so you can just
  use OO syntax and stop worrying about whether your function's caller
  handed you a string, a globref, or a FileHandle.


pkgId: b5ec16bd039f98555aa21ae90cd9ba19469fc11a49a481b514879945c37305f5
name: local-perl-IPC-Cmd
arch: noarch
version: 0.70
epoch: 1
release: 162.ep
summary: Finding and running system commands made easy
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-IPC-Cmd-0.70-162.ep.noarch.rpm
checksum_type: sha256
description:
  IPC::Cmd allows you to run commands, interactively if desired, in a platform
  independent way, but have them still work.


pkgId: 0234bd812afda3340e47d4c5cc700395923f6fe5c4c8e3089185fa0f04891c33
name: local-perl-IPC-Run3
arch: noarch
version: 0.044
epoch: 0
release: 1
summary: IPC-Run3 - run a subprocess with input/ouput redirection
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Barrie Slaymaker <barries@slaysys.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-IPC-Run3-0.044-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-IPC-Run3-0.044-1.noarch.rpm
checksum_type: sha256
description:
  This module allows you to run a subprocess and redirect stdin, stdout,
  and/or stderr to files and perl data structures.  It aims to satisfy 99% of the
  need for using C<system>, C<qx>, and C<open3>
  with a simple, extremely Perlish API.

  Speed, simplicity, and portability are paramount.  (That's speed of Perl code;
  which is often much slower than the kind of buffered I/O that this module uses
  to spool input to and output from the child command.)


pkgId: 3cb5f7f14812d2ae18eac42277d735550ff0391ce8e137e78b387a254b95509b
name: local-perl-Image-Scale
arch: x86_64
version: 0.08
epoch: 0
release: 1
summary: Image-Scale - Fast, high-quality fixed-point image resizing
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Grundman <andy@hybridized.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Image-Scale-0.08-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Image-Scale-0.08-1.x86_64.rpm
checksum_type: sha256
description:
  This module implements several resizing algorithms with a focus on low overhead,
  speed and minimal features. Algorithms available are:

    GD's copyResampled (floating-point)
    GD's copyResampled fixed-point (useful on embedded devices/NAS devices)
    GraphicsMagick's assortment of resize filters (floating-point)
    GraphicsMagick's Triangle filter in fixed-point

  Supported image formats include JPEG, GIF, PNG, and BMP for input, and
  JPEG and PNG for output.

  This module came about because we needed to improve the very slow performance of
  floating-point resizing algorithms on platforms without a floating-point
  unit, such as ARM devices like the SheevaPlug, and the Sparc-based ReadyNAS Duo.
  Previously it would take many seconds to resize using GD on the ReadyNAS but the
  conversion to fixed-point with a little assembly code brings this down to the range of
  well under 1 second.

  GD is also incredibly difficult to build on platforms such as Windows so we
  needed a replacement.

  Normal platforms will also see improvement, by removing all of the GD overhead this
  version of copyResampled is around 3 times faster while also using less memory.

  The fixed-point versions have an accuracy to around 4 decimal places so the quality
  of floating-point vs. fixed is essentially identical.


pkgId: f93e021a4959e93875ce4d677a907a2185eb09554f3bffda750068a8082ad529
name: local-perl-Image-Size
arch: noarch
version: 3.230
epoch: 0
release: 1
summary: Image-Size - read the dimensions of an image in several popular formats
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: J Ray C <rjray@blackperl.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Image-Size-3.230-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Image-Size-3.230-1.noarch.rpm
checksum_type: sha256
description:
  The B<Image::Size> library is based upon the C<wwwis> script written by
  Alex Knowles I<(alex@ed.ac.uk)>, a tool to examine HTML and add 'width' and
  'height' parameters to image tags. The sizes are cached internally based on
  file name, so multiple calls on the same file name (such as images used
  in bulleted lists, for example) do not result in repeated computations.


pkgId: 4d0946d3c7c612c00f767d35c237b057de63d4c0e317b3f0aaf240cb99e79d93
name: local-perl-JSON
arch: noarch
version: 2.53
epoch: 0
release: 1
summary: JSON - JSON (JavaScript Object Notation) encoder/decoder
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Makamaka Hannyaharamitu, E<lt>makamaka[at]cpan.orgE<gt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-JSON-2.53-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-JSON-2.53-1.noarch.rpm
checksum_type: sha256
description:
  ************************** CAUTION ********************************
   * This is 'JSON module version 2' and there are many differences  *
   * to version 1.xx                                                 *
   * Please check your applications useing old version.              *
   *   See to 'INCOMPATIBLE CHANGES TO OLD VERSION'                  *
   *******************************************************************

  JSON (JavaScript Object Notation) is a simple data format.
  See to L<http://www.json.org/> and C<RFC4627>(L<http://www.ietf.org/rfc/rfc4627.txt>).

  This module converts Perl data structures to JSON and vice versa using either
  L<JSON::XS> or L<JSON::PP>.

  JSON::XS is the fastest and most proper JSON module on CPAN which must be
  compiled and installed in your environment.
  JSON::PP is a pure-Perl module which is bundled in this distribution and
  has a strong compatibility to JSON::XS.

  This module try to use JSON::XS by default and fail to it, use JSON::PP instead.
  So its features completely depend on JSON::XS or JSON::PP.

  See to L<BACKEND MODULE DECISION>.

  To distinguish the module name 'JSON' and the format type JSON,
  the former is quoted by CE<lt>E<gt> (its results vary with your using media),
  and the latter is left just as it is.

  Module name : C<JSON>

  Format type : JSON


pkgId: 873a1bc9315ed644836f7a4a6a36638a20f3a970d77028a037d3cb23b6ec3ba6
name: local-perl-JSON-Any
arch: noarch
version: 1.30
epoch: 0
release: 1
summary: JSON-Any - Wrapper Class for the various JSON classes.
description: None.
url: http://www.cpan.org
rpm_license: Artistic
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-JSON-Any-1.30-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-JSON-Any-1.30-1.noarch.rpm
checksum_type: sha256
rpm_vendor:
  Chris Thompson <cthom@cpan.org>, Chris Prather <chris@prather.org>, Robin Berjon <robin@berjon.com>, Marc Mims <marc@questright.com>, Tomas Doran <bobtfish@bobtfish.net>


pkgId: e3ecf9270813fd170b56b6d996bee73d3346e95ca3a30aa392fe80c3da54d5df
name: local-perl-JSON-DWIW
arch: x86_64
version: 0.47
epoch: 0
release: 1
summary: JSON-DWIW - JSON converter that does what I want
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: DON OWENS <don@regexguy.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-JSON-DWIW-0.47-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-JSON-DWIW-0.47-1.x86_64.rpm
checksum_type: sha256
description:
  Other JSON modules require setting several parameters before
  calling the conversion methods to do what I want.  This module
  does things by default that I think should be done when working
  with JSON in Perl.  This module also encodes and decodes faster
  than L<JSON>.pm and L<JSON::Syck> in my benchmarks.

  This means that any piece of data in Perl (assuming it's valid
  unicode) will get converted to something in JSON instead of
  throwing an exception.  It also means that output will be strict
  JSON, while accepted input will be flexible, without having to
  set any options.

  For a list of changes in recent versions, see the documentation
  for L<JSON::DWIW::Changes>.

  This module can be downloaded from L<http://www.cpan.org/authors/id/D/DO/DOWENS/>.


pkgId: e754996cf4814fc7b46f1e28285616d5f707cf09d2e4000638c4470feb22e200
name: local-perl-JSON-XS
arch: x86_64
version: 2.32
epoch: 0
release: 1
summary: JSON-XS - JSON serialising/deserialising, done correctly and fast
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Marc Lehmann <schmorp@schmorp.de>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-JSON-XS-2.32-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-JSON-XS-2.32-1.x86_64.rpm
checksum_type: sha256
description:
  This module converts Perl data structures to JSON and vice versa. Its
  primary goal is to be I<correct> and its secondary goal is to be
  I<fast>. To reach the latter goal it was written in C.

  Beginning with version 2.0 of the JSON module, when both JSON and
  JSON::XS are installed, then JSON will fall back on JSON::XS (this can be
  overridden) with no overhead due to emulation (by inheriting constructor
  and methods). If JSON::XS is not available, it will fall back to the
  compatible JSON::PP module as backend, so using JSON instead of JSON::XS
  gives you a portable JSON API that can be fast when you need and doesn't
  require a C compiler when that is a problem.

  As this is the n-th-something JSON module on CPAN, what was the reason
  to write yet another JSON module? While it seems there are many JSON
  modules, none of them correctly handle all corner cases, and in most cases
  their maintainers are unresponsive, gone missing, or not listening to bug
  reports for other reasons.

  See MAPPING, below, on how JSON::XS maps perl values to JSON values and
  vice versa.


pkgId: e226d4a5b897316300f8d0293fd223b31e0075a91579ba062baf1e5e8d909bf6
name: local-perl-Jcode
arch: x86_64
version: 2.07
epoch: 0
release: 1
summary: Jcode - Japanese Charset Handler
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Dan Kogai <dankogai@dan.co.jp>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Jcode-2.07-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Jcode-2.07-1.x86_64.rpm
checksum_type: sha256
description:
  B<<Japanese document is now available as L<Jcode::Nihongo>. >>

  Jcode.pm supports both object and traditional approach.
  With object approach, you can go like;

    $iso_2022_jp = Jcode->new($str)->h2z->jis;

  Which is more elegant than:

    $iso_2022_jp = $str;
    &jcode::convert(\$iso_2022_jp, 'jis', &jcode::getcode(\$str), "z");

  For those unfamiliar with objects, Jcode.pm still supports C<getcode()>
  and C<convert().>

  If the perl version is 5.8.1, Jcode acts as a wrapper to L<Encode>,
  the standard charset handler module for Perl 5.8 or later.


pkgId: 43e399a37de28ab97c1ca59beb3079d09e85d99c6bb036879b773778e4b98b7f
name: local-perl-LWES
arch: x86_64
version: 0.01
epoch: 0
release: 1
summary: LWES - Perl extension for the Light Weight Event System
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Anthony Molinaro <Eltmolinaro@users.sourceforge.netEgt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-LWES-0.01-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-LWES-0.01-1.x86_64.rpm
checksum_type: sha256
description:
  This is the Perl interface to the Light Weight Event System.  The
  Light Weight Event System is a UDP-based communication toolkit with
  built-in serialization, formatting, and type-checking.


pkgId: fa97c54be8f88f2c62c220aff4b4f8461d5ab0c594ec48473e57f5ec8e855aa3
name: local-perl-LWP-MediaTypes
arch: noarch
version: 6.01
epoch: 0
release: 1
summary: LWP-MediaTypes - guess media type for a file or a URL
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-LWP-MediaTypes-6.01-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-LWP-MediaTypes-6.01-1.noarch.rpm
checksum_type: sha256
description:
  This module provides functions for handling media (also known as
  MIME) types and encodings.  The mapping from file extensions to media
  types is defined by the F<media.types> file.  If the F<~/.media.types>
  file exists it is used instead.
  For backwards compatibility we will also look for F<~/.mime.types>.

  The following functions are exported by default:

  =over 4

  =item guess_media_type( $filename )

  =item guess_media_type( $uri )

  =item guess_media_type( $filename_or_uri, $header_to_modify )

  This function tries to guess media type and encoding for a file or a URI.
  It returns the content type, which is a string like C<"text/html">.
  In array context it also returns any content encodings applied (in the
  order used to encode the file).  You can pass a URI object
  reference, instead of the file name.

  If the type can not be deduced from looking at the file name,
  then guess_media_type() will let the C<-T> Perl operator take a look.
  If this works (and C<-T> returns a TRUE value) then we return
  I<text/plain> as the type, otherwise we return
  I<application/octet-stream> as the type.

  The optional second argument should be a reference to a HTTP::Headers
  object or any object that implements the $obj->header method in a
  similar way.  When it is present the values of the
  'Content-Type' and 'Content-Encoding' will be set for this header.

  =item media_suffix( $type, ... )

  This function will return all suffixes that can be used to denote the
  specified media type(s).  Wildcard types can be used.  In a scalar
  context it will return the first suffix found. Examples:

    @suffixes = media_suffix('image/*', 'audio/basic');
    $suffix = media_suffix('text/html');

  =back

  The following functions are only exported by explicit request:

  =over 4

  =item add_type( $type, @exts )

  Associate a list of file extensions with the given media type.
  Example:

      add_type("x-world/x-vrml" => qw(wrl vrml));

  =item add_encoding( $type, @ext )

  Associate a list of file extensions with an encoding type.
  Example:

   add_encoding("x-gzip" => "gz");

  =item read_media_types( @files )

  Parse media types files and add the type mappings found there.
  Example:

      read_media_types("conf/mime.types");

  =back


pkgId: ca792f6746631fb81b75650b738327948b28e629eaa1f98b5e913fffaf512ca2
name: local-perl-LWP-Protocol-https
arch: noarch
version: 6.02
epoch: 0
release: 1
summary: LWP-Protocol-https - Provide https support for LWP::UserAgent
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-LWP-Protocol-https-6.02-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-LWP-Protocol-https-6.02-1.noarch.rpm
checksum_type: sha256
description:
  The LWP::Protocol::https module provide support for using https schemed
  URLs with LWP.  This module is a plug-in to the LWP protocol handling, so
  you don't use it directly.  Once the module is installed LWP is able
  to access sites using HTTP over SSL/TLS.

  If hostname verification is requested by LWP::UserAgent's C<ssl_opts>, and
  neither C<SSL_ca_file> nor C<SSL_ca_path> is set, then C<SSL_ca_file> is
  implied to be the one provided by Mozilla::CA.  If the Mozilla::CA module
  isn't available SSL requests will fail.  Either install this module, set up an
  alternative C<SSL_ca_file> or disable hostname verification.

  This module used to be bundled with the libwww-perl, but it was unbundled in
  v6.02 in order to be able to declare its dependencies properly for the CPAN
  tool-chain.  Applications that need https support can just declare their
  dependency on LWP::Protocol::https and will no longer need to know what
  underlying modules to install.


pkgId: 33ff26695e4fcfe8b80b40897a139f81a63f96b748f9d244574a99311f77cd57
name: local-perl-List-MoreUtils
arch: x86_64
version: 0.33
epoch: 0
release: 1
summary: List-MoreUtils - Provide the stuff missing in List::Util
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tassilo von Parseval <tassilo.von.parseval@rwth-aachen.de>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-List-MoreUtils-0.33-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-List-MoreUtils-0.33-1.x86_64.rpm
checksum_type: sha256
description:
  B<List::MoreUtils> provides some trivial but commonly needed functionality on
  lists which is not going to go into L<List::Util>.

  All of the below functions are implementable in only a couple of lines of Perl
  code. Using the functions from this module however should give slightly better
  performance as everything is implemented in C. The pure-Perl implementation of
  these functions only serves as a fallback in case the C portions of this module
  couldn't be compiled on this machine.

  =over 4

  =item any BLOCK LIST

  Returns a true value if any item in LIST meets the criterion given through
  BLOCK. Sets C<$_> for each item in LIST in turn:

      print "At least one value undefined"
          if any { ! defined($_) } @list;

  Returns false otherwise, or if LIST is empty.

  =item all BLOCK LIST

  Returns a true value if all items in LIST meet the criterion given through
  BLOCK, or if LIST is empty. Sets C<$_> for each item in LIST in turn:

      print "All items defined"
          if all { defined($_) } @list;

  Returns false otherwise.

  =item none BLOCK LIST

  Logically the negation of C<any>. Returns a true value if no item in LIST meets
  the criterion given through BLOCK, or if LIST is empty. Sets C<$_> for each item
  in LIST in turn:

      print "No value defined"
          if none { defined($_) } @list;

  Returns false otherwise.

  =item notall BLOCK LIST

  Logically the negation of C<all>. Returns a true value if not all items in LIST
  meet the criterion given through BLOCK. Sets C<$_> for each item in LIST in
  turn:

      print "Not all values defined"
          if notall { defined($_) } @list;

  Returns false otherwise, or if LIST is empty.

  =item true BLOCK LIST

  Counts the number of elements in LIST for which the criterion in BLOCK is true.
  Sets C<$_> for  each item in LIST in turn:

      printf "%i item(s) are defined", true { defined($_) } @list;

  =item false BLOCK LIST

  Counts the number of elements in LIST for which the criterion in BLOCK is false.
  Sets C<$_> for each item in LIST in turn:

      printf "%i item(s) are not defined", false { defined($_) } @list;

  =item firstidx BLOCK LIST

  =item first_index BLOCK LIST

  Returns the index of the first element in LIST for which the criterion in BLOCK
  is true. Sets C<$_> for each item in LIST in turn:

      my @list = (1, 4, 3, 2, 4, 6);
      printf "item with index %i in list is 4", firstidx { $_ == 4 } @list;
      __END__
      item with index 1 in list is 4

  Returns C<-1> if no such item could be found.

  C<first_index> is an alias for C<firstidx>.

  =item lastidx BLOCK LIST

  =item last_index BLOCK LIST

  Returns the index of the last element in LIST for which the criterion in BLOCK
  is true. Sets C<$_> for each item in LIST in turn:

      my @list = (1, 4, 3, 2, 4, 6);
      printf "item with index %i in list is 4", lastidx { $_ == 4 } @list;
      __END__
      item with index 4 in list is 4

  Returns C<-1> if no such item could be found.

  C<last_index> is an alias for C<lastidx>.

  =item insert_after BLOCK VALUE LIST

  Inserts VALUE after the first item in LIST for which the criterion in BLOCK is
  true. Sets C<$_> for each item in LIST in turn.

      my @list = qw/This is a list/;
      insert_after { $_ eq "a" } "longer" => @list;
      print "@list";
      __END__
      This is a longer list

  =item insert_after_string STRING VALUE LIST

  Inserts VALUE after the first item in LIST which is equal to STRING.

      my @list = qw/This is a list/;
      insert_after_string "a", "longer" => @list;
      print "@list";
      __END__
      This is a longer list

  =item apply BLOCK LIST

  Applies BLOCK to each item in LIST and returns a list of the values after BLOCK
  has been applied. In scalar context, the last element is returned.  This
  function is similar to C<map> but will not modify the elements of the input
  list:

      my @list = (1 .. 4);
      my @mult = apply { $_ *= 2 } @list;
      print "\@list = @list\n";
      print "\@mult = @mult\n";
      __END__
      @list = 1 2 3 4
      @mult = 2 4 6 8

  Think of it as syntactic sugar for

      for (my @mult = @list) { $_ *= 2 }

  =item before BLOCK LIST

  Returns a list of values of LIST upto (and not including) the point where BLOCK
  returns a true value. Sets C<$_> for each element in LIST in turn.

  =item before_incl BLOCK LIST

  Same as C<before> but also includes the element for which BLOCK is true.

  =item after BLOCK LIST

  Returns a list of the values of LIST after (and not including) the point
  where BLOCK returns a true value. Sets C<$_> for each element in LIST in turn.

      @x = after { $_ % 5 == 0 } (1..9);    # returns 6, 7, 8, 9

  =item after_incl BLOCK LIST

  Same as C<after> but also inclues the element for which BLOCK is true.

  =item indexes BLOCK LIST

  Evaluates BLOCK for each element in LIST (assigned to C<$_>) and returns a list
  of the indices of those elements for which BLOCK returned a true value. This is
  just like C<grep> only that it returns indices instead of values:

      @x = indexes { $_ % 2 == 0 } (1..10);   # returns 1, 3, 5, 7, 9

  =item firstval BLOCK LIST

  =item first_value BLOCK LIST

  Returns the first element in LIST for which BLOCK evaluates to true. Each
  element of LIST is set to C<$_> in turn. Returns C<undef> if no such element
  has been found.

  C<first_val> is an alias for C<firstval>.

  =item lastval BLOCK LIST

  =item last_value BLOCK LIST

  Returns the last value in LIST for which BLOCK evaluates to true. Each element
  of LIST is set to C<$_> in turn. Returns C<undef> if no such element has been
  found.

  C<last_val> is an alias for C<lastval>.

  =item pairwise BLOCK ARRAY1 ARRAY2

  Evaluates BLOCK for each pair of elements in ARRAY1 and ARRAY2 and returns a
  new list consisting of BLOCK's return values. The two elements are set to C<$a>
  and C<$b>.  Note that those two are aliases to the original value so changing
  them will modify the input arrays.

      @a = (1 .. 5);
      @b = (11 .. 15);
      @x = pairwise { $a + $b } @a, @b;	# returns 12, 14, 16, 18, 20

      
      @a = qw/a b c/;
      @b = qw/1 2 3/;
      @x = pairwise { ($a, $b) } @a, @b;	# returns a, 1, b, 2, c, 3

  =item each_array ARRAY1 ARRAY2 ...

  Creates an array iterator to return the elements of the list of arrays ARRAY1,
  ARRAY2 throughout ARRAYn in turn.  That is, the first time it is called, it
  returns the first element of each array.  The next time, it returns the second
  elements.  And so on, until all elements are exhausted.

  This is useful for looping over more than one array at once:

      my $ea = each_array(@a, @b, @c);
      while ( my ($a, $b, $c) = $ea->() )   { .... }

  The iterator returns the empty list when it reached the end of all arrays.

  If the iterator is passed an argument of 'C<index>', then it retuns
  the index of the last fetched set of values, as a scalar.

  =item each_arrayref LIST

  Like each_array, but the arguments are references to arrays, not the
  plain arrays.

  =item natatime EXPR, LIST

  Creates an array iterator, for looping over an array in chunks of
  C<$n> items at a time.  (n at a time, get it?).  An example is
  probably a better explanation than I could give in words.

  Example:

      my @x = ('a' .. 'g');
      my $it = natatime 3, @x;
      while (my @vals = $it->())
      {
          print "@vals\n";
      }

  This prints

      a b c
      d e f
      g

  =item mesh ARRAY1 ARRAY2 [ ARRAY3 ... ]

  =item zip ARRAY1 ARRAY2 [ ARRAY3 ... ]

  Returns a list consisting of the first elements of each array, then
  the second, then the third, etc, until all arrays are exhausted.

  Examples:

      @x = qw/a b c d/;
      @y = qw/1 2 3 4/;
      @z = mesh @x, @y;	    # returns a, 1, b, 2, c, 3, d, 4

      @a = ('x');
      @b = ('1', '2');
      @c = qw/zip zap zot/;
      @d = mesh @a, @b, @c;   # x, 1, zip, undef, 2, zap, undef, undef, zot

  C<zip> is an alias for C<mesh>.

  =item uniq LIST

  =item distinct LIST

  Returns a new list by stripping duplicate values in LIST. The order of
  elements in the returned list is the same as in LIST. In scalar context,
  returns the number of unique elements in LIST.

      my @x = uniq 1, 1, 2, 2, 3, 5, 3, 4; # returns 1 2 3 5 4
      my $x = uniq 1, 1, 2, 2, 3, 5, 3, 4; # returns 5

  =item minmax LIST

  Calculates the minimum and maximum of LIST and returns a two element list with
  the first element being the minimum and the second the maximum. Returns the
  empty list if LIST was empty.

  The C<minmax> algorithm differs from a naive iteration over the list where each
  element is compared to two values being the so far calculated min and max value
  in that it only requires 3n/2 - 2 comparisons. Thus it is the most efficient
  possible algorithm.

  However, the Perl implementation of it has some overhead simply due to the fact
  that there are more lines of Perl code involved. Therefore, LIST needs to be
  fairly big in order for C<minmax> to win over a naive implementation. This
  limitation does not apply to the XS version.

  =item part BLOCK LIST

  Partitions LIST based on the return value of BLOCK which denotes into which
  partition the current value is put.

  Returns a list of the partitions thusly created. Each partition created is a
  reference to an array.

      my $i = 0;
      my @part = part { $i++ % 2 } 1 .. 8;   # returns [1, 3, 5, 7], [2, 4, 6, 8]

  You can have a sparse list of partitions as well where non-set partitions will
  be undef:

      my @part = part { 2 } 1 .. 10;	    # returns undef, undef, [ 1 .. 10 ]

  Be careful with negative values, though:

      my @part = part { -1 } 1 .. 10;
      __END__
      Modification of non-creatable array value attempted, subscript -1 ...

  Negative values are only ok when they refer to a partition previously created:

      my @idx  = ( 0, 1, -1 );
      my $i    = 0;
      my @part = part { $idx[$++ % 3] } 1 .. 8; # [1, 4, 7], [2, 3, 5, 6, 8]

  =back


pkgId: 8d1a884635a30dbd8115939b1f2ff3e7b58ad962292305d280df6b54eaae511e
name: local-perl-Locale-Maketext-Simple
arch: noarch
version: 0.21
epoch: 1
release: 162.ep
summary: Simple interface to Locale::Maketext::Lexicon
url: http://www.perl.org/
rpm_license: MIT
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Locale-Maketext-Simple-0.21-162.ep.noarch.rpm
checksum_type: sha256
description:
  This module is a simple wrapper around Locale::Maketext::Lexicon, designed
  to alleviate the need of creating Language Classes for module authors.


pkgId: 4f233316587dc0639820011e514d714652380496a3358c7974cf2e15a883b453
name: local-perl-Log-Dispatch-FileRotate
arch: noarch
version: 1.19
epoch: 0
release: 1
summary: Log-Dispatch-FileRotate - Log to files that archive/rotate themselves
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: "Mark Pfeiffer" <markpf@mlp-consulting.com.au>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Log-Dispatch-FileRotate-1.19-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Log-Dispatch-FileRotate-1.19-1.noarch.rpm
checksum_type: sha256
description:
  This module provides a simple object for logging to files under the
  Log::Dispatch::* system, and automatically rotating them according to
  different constraints. This is basically a Log::Dispatch::File wrapper
  with additions. To that end the arguments

  	name, min_level, filename and  mode

  behave the same as Log::Dispatch::File. So see its man page
  (perldoc Log::Dispatch::File)

  The arguments size and max specify the maximum size and maximum
  number of log files created. The size defaults to 10M and the max number
  of files defaults to 1. If DatePattern is not defined then we default to
  working in size mode. That is, use size values for deciding when to rotate.

  Once DatePattern is defined FileRotate will move into time mode. Once
  this happens file rotation ignores size constraints and uses the defined
  date pattern constraints.

  If you setup a config file using Log::Log4perl::init_and_watch() or the
  like, you can switch between modes just by commenting out the DatePattern
  line.

  When using DatePattern make sure TZ is defined correctly and that the TZ
  you use is understood by Date::Manip. We use Date::Manip to generate our
  recurrences. Bad TZ equals bad recurrences equals surprises! Read the
  Date::Manip man page for more details on TZ.

  DatePattern will default to a daily rotate if your entered pattern is
  incorrect. You will also get a warning message.

  If you have multiple writers that were started at different times you
  will find each writer will try to rotate the log file at a recurrence
  calculated from its start time. To sync all the writers just use a config
  file and update it after starting your last writer. This will cause
  Log::Dispatch::FileRotate->new() to be called by each of the writers
  close to the same time, and if your recurrences aren't too close together
  all should sync up just nicely.

  I initially aasumed a long runinng process but it seems people are using
  this module as part of short running CGI programs. So, now we look at the
  last modified time stamp of the log file and compare it to a previous
  occurance of a DatePattern, on startup only. If the file stat shows
  the mtime to be earlier than the previous recurrance then I rotate the
  log file.

  We handle multiple writers using flock().


pkgId: bc630d746a3e02b3124d8e76af059d0d070c47e8d007af5b016e724b371f07f7
name: local-perl-Log-Log4perl
arch: noarch
version: 1.38
epoch: 0
release: 1
summary: Log-Log4perl - Log4j implementation for Perl
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Mike Schilli <m@perlmeister.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Log-Log4perl-1.38-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Log-Log4perl-1.38-1.noarch.rpm
checksum_type: sha256
description:
  Log::Log4perl lets you remote-control and fine-tune the logging behaviour
  of your system from the outside. It implements the widely popular
  (Java-based) Log4j logging package in pure Perl.

  B<For a detailed tutorial on Log::Log4perl usage, please read>

      http://www.perl.com/pub/a/2002/09/11/log4perl.html

  Logging beats a debugger if you want to know what's going on
  in your code during runtime. However, traditional logging packages
  are too static and generate a flood of log messages in your log files
  that won't help you.

  C<Log::Log4perl> is different. It allows you to control the number of
  logging messages generated at three different levels:

  =over 4

  =item *

  At a central location in your system (either in a configuration file or
  in the startup code) you specify I<which components> (classes, functions)
  of your system should generate logs.

  =item *

  You specify how detailed the logging of these components should be by
  specifying logging I<levels>.

  =item *

  You also specify which so-called I<appenders> you want to feed your
  log messages to ("Print it to the screen and also append it to /tmp/my.log")
  and which format ("Write the date first, then the file name and line
  number, and then the log message") they should be in.

  =back

  This is a very powerful and flexible mechanism. You can turn on and off
  your logs at any time, specify the level of detail and make that
  dependent on the subsystem that's currently executed.

  Let me give you an example: You might
  find out that your system has a problem in the
  C<MySystem::Helpers::ScanDir>
  component. Turning on detailed debugging logs all over the system would
  generate a flood of useless log messages and bog your system down beyond
  recognition. With C<Log::Log4perl>, however, you can tell the system:
  "Continue to log only severe errors to the log file. Open a second
  log file, turn on full debug logs in the C<MySystem::Helpers::ScanDir>
  component and dump all messages originating from there into the new
  log file". And all this is possible by just changing the parameters
  in a configuration file, which your system can re-read even
  while it's running!


pkgId: 9bcec01de25d04f5194b662ab07f80db9b3cd26fc9782fc91daceeb6ebec3a5c
name: local-perl-Log-Message
arch: noarch
version: 0.04
epoch: 1
release: 162.ep
summary: Generic message storage mechanism
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Log-Message-0.04-162.ep.noarch.rpm
checksum_type: sha256
description:
  Log::Message is a generic message storage mechanism. It allows you to store
  messages on a stack -- either shared or private -- and assign meta-data to it.
  Some meta-data will automatically be added for you, like a timestamp and a
  stack trace, but some can be filled in by the user, like a tag by which to
  identify it or group it, and a level at which to handle the message (for
  example, log it, or die with it).


pkgId: 4329049cedc7cb0222c390b9f75dca9819e9ce7fa87f373e9e7105eb993054c3
name: local-perl-MD5
arch: noarch
version: 2.03
epoch: 0
release: 1
summary: MD5 - Perl interface to the MD5 Message-Digest Algorithm
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: gaas@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-MD5-2.03-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MD5-2.03-1.noarch.rpm
checksum_type: sha256
description:
  The C<MD5> module is B<depreciated>.  Use C<Digest::MD5> instead.

  The current C<MD5> module is just a wrapper around the C<Digest::MD5>
  module.  It is provided so that legacy code that rely on the old
  interface still work and get the speed benefit of the new module.

  In addition to the methods provided for C<Digest::MD5> objects, this
  module provide the class methods MD5->hash() and MD5->hexhash() that
  do the same as the md5() and md5_hex() functions provided by
  C<Digest::MD5>.


pkgId: 02bd84c2ca01542434757fa4385ebc8bff0c0753f44865695f70bafff11d9f7b
name: local-perl-MIME-Base64-URLSafe
arch: noarch
version: 0.01
epoch: 0
release: 1
summary: MIME-Base64-URLSafe - Perl version of Python's URL-safe base64 codec
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Kazuho Oku <kazuho ___at___ labs.cybozu.co.jp>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-MIME-Base64-URLSafe-0.01-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MIME-Base64-URLSafe-0.01-1.noarch.rpm
checksum_type: sha256
description:
  This module is a perl version of python's URL-safe base64 encoder / decoder.

  When embedding binary data in URL, it is preferable to use base64 encoding.  However, two characters ('+' and '/') used in the standard base64 encoding have special meanings in URLs, often leading to re-encoding with URL-encoding, or worse, interoperability problems.

  To overcome the problem, the module provides a variation of base64 codec compatible with python's urlsafe_b64encode / urlsafe_b64decode.

  Modification rules from base64:

      use '-' and '_' instead of '+' and '/'
      no line feeds
      no trailing equals (=)

  The following functions are provided:

      urlsafe_b64encode($str)
      urlsafe_b64decode($str)

  If you prefer not to import these routines to your namespace, you can call them as:

      use MIME::Base64::URLSafe ();
      $encoded = MIME::Base64::URLSafe::encode($decoded);
      $decoded = MIME::Base64::URLSafe::decode($encoded);


pkgId: 73273f166697f04e7ed537f01b69f4c5a898e04a959a305d27342a7dc9a6c49e
name: local-perl-MIME-Lite
arch: noarch
version: 3.027
epoch: 0
release: 1
summary: MIME-Lite - low-calorie MIME generator
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Eryq <Feryq@zeegee.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-MIME-Lite-3.027-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MIME-Lite-3.027-1.noarch.rpm
checksum_type: sha256
description:
  In the never-ending quest for great taste with fewer calories,
  we proudly present: I<MIME::Lite>.

  MIME::Lite is intended as a simple, standalone module for generating
  (not parsing!) MIME messages... specifically, it allows you to
  output a simple, decent single- or multi-part message with text or binary
  attachments.  It does not require that you have the Mail:: or MIME::
  modules installed, but will work with them if they are.

  You can specify each message part as either the literal data itself (in
  a scalar or array), or as a string which can be given to open() to get
  a readable filehandle (e.g., "<filename" or "somecommand|").

  You don't need to worry about encoding your message data:
  this module will do that for you.  It handles the 5 standard MIME encodings.


pkgId: c5b41068c0d6a29b475ed8d0ea6b9adb926243475b1b852a9fd343953b7c10b2
name: local-perl-Mail-POP3Client
arch: noarch
version: 2.18
epoch: 0
release: 1
summary: Mail-POP3Client - Perl 5 module to talk to a POP3 (RFC1939) server
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sean Dowd <pop3client@dowds.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Mail-POP3Client-2.18-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-POP3Client-2.18-1.noarch.rpm
checksum_type: sha256
description:
  This module implements an Object-Oriented interface to a POP3 server.
  It implements RFC1939 (http://www.faqs.org/rfcs/rfc1939.html)


pkgId: 10a2e4503a3cbeaace4565cad12a9a56c3653734eec8d18e9b30c592438ce276
name: local-perl-Mail-RFC822-Address
arch: noarch
version: 0.3
epoch: 0
release: 1
summary: Mail-RFC822-Address - Perl extension for validating email addresses
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Paul Warren <pdw@ex-parrot.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Mail-RFC822-Address-0.3-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-RFC822-Address-0.3-1.noarch.rpm
checksum_type: sha256
description:
  Mail::RFC822::Address validates email addresses against the grammar described
  in RFC 822 using regular expressions.  How to validate a user supplied email
  address is a FAQ (see perlfaq9): the only sure way to see if a supplied email
  address is genuine is to send an email to it and see if the user recieves it.
  The one useful check that can be performed on an address is to check that the
  email address is syntactically valid.  That is what this module does.

  This module is functionally equivalent to RFC::RFC822::Address, but uses
  regular expressions rather than the Parse::RecDescent parser.  This means that
  startup time is greatly reduced making it suitable for use in transient scripts
  such as CGI scripts.


pkgId: b889cb2977f663ab1a46233473eb3095d8d965cbe5d162936778c434941b2b2e
name: local-perl-Mail-Sender
arch: noarch
version: 0.8.21
epoch: 0
release: 1
summary: Mail-Sender - Send mails with attachments through a SMTP server, socket()s based.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jan Krynicky (Jenda@Krynicky.cz)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Mail-Sender-0.8.21-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-Sender-0.8.21-1.noarch.rpm
checksum_type: sha256
description:
  C<Mail::Sender> provides an object oriented interface to sending mails.
  It doesn't need any outer program. It connects to a mail server
  directly from Perl, using Socket.

  Sends mails directly from Perl through a socket connection.


pkgId: 36bbe3b433d7f51bdf8d7323a85cda2a67da1e4066a1d6464d1701154ee73b19
name: local-perl-Mail-Sendmail
arch: noarch
version: 0.79_16
epoch: 0
release: 1
summary: Mail-Sendmail - Simple platform independent mailer
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Milivoj Ivkovic <mi _at_ alma.ch>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Mail-Sendmail-0.79_16-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-Sendmail-0.79_16-1.noarch.rpm
checksum_type: sha256
description:
  Simple platform independent e-mail from your perl script. Only requires
  Perl 5 and a network connection.

  Mail::Sendmail takes a hash with the message to send and sends it to your
  mail server. It is intended to be very easy to setup and
  use. See also L<"FEATURES"> below, and as usual, read this documentation.

  There is also a FAQ (see L<"NOTES">).


pkgId: 8501434ffec749c74a73140a55c35d378087025e3bf0a824f62d3e5f37bef390
name: local-perl-Math-Round
arch: noarch
version: 0.06
epoch: 0
release: 1
summary: Math-Round - Perl extension for rounding numbers
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: by Geoffrey Rommel <EltGROMMEL@cpan.orgEgt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Math-Round-0.06-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Math-Round-0.06-1.noarch.rpm
checksum_type: sha256
description:
  B<Math::Round> supplies functions that will round numbers in different
  ways.  The functions B<round> and B<nearest> are exported by
  default; others are available as described below.  "use ... qw(:all)"
  exports all functions.


pkgId: d1e8c744b0d1974a2efa04efaf89607bcf6b2576a063b127c009b00880193013
name: local-perl-Module-Build
arch: noarch
version: 0.3800
epoch: 1
release: 162.ep
summary: Perl module for building and installing Perl modules
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Module-Build-0.3800-162.ep.noarch.rpm
checksum_type: sha256
description:
  Module::Build is a system for building, testing, and installing Perl modules.
  It is meant to be an alternative to ExtUtils::MakeMaker.  Developers may alter
  the behavior of the module through subclassing in a much more straightforward
  way than with MakeMaker. It also does not require a make on your system - most
  of the Module::Build code is pure-perl and written in a very cross-platform
  way. In fact, you don't even need a shell, so even platforms like MacOS
  (traditional) can use it fairly easily. Its only prerequisites are modules that
  are included with perl 5.6.0, and it works fine on perl 5.005 if you can
  install a few additional modules.


pkgId: d7da88e36f16e3bd2051b361921838392e7b53a0e60fa7f5d9e50629aa578e6f
name: local-perl-Module-CoreList
arch: noarch
version: 2.49_01
epoch: 0
release: 162.ep
summary: Perl core modules indexed by perl versions
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Languages
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Module-CoreList-2.49_01-162.ep.noarch.rpm
checksum_type: sha256
description:
  Module::CoreList contains the hash of hashes %Module::CoreList::version, this
  is keyed on perl version as indicated in $].  The second level hash is module
  => version pairs.


pkgId: 78a42044b23ae95c9ae75d4ffae47c296427ac3820f78de240ac9a0f115c6ceb
name: local-perl-Module-Load
arch: noarch
version: 0.18
epoch: 1
release: 162.ep
summary: Runtime require of both modules and files
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Module-Load-0.18-162.ep.noarch.rpm
checksum_type: sha256
description:
  Module::Load eliminates the need to know whether you are trying to require
  either a file or a module.


pkgId: c20916c1319e37b99f9e7f414cbb7b2e86ece53a7c06011c8c6ff592bc47221f
name: local-perl-Module-Load-Conditional
arch: noarch
version: 0.44
epoch: 0
release: 162.ep
summary: Looking up module information / loading at runtime
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Module-Load-Conditional-0.44-162.ep.noarch.rpm
checksum_type: sha256
description:
  Module::Load::Conditional provides simple ways to query and possibly load any
  of the modules you have installed on your system during runtime.


pkgId: 79de9cb8461820a9612b30bd781dc7d2b799095d94863de872f36f85abb51b86
name: local-perl-Module-Loaded
arch: noarch
version: 0.06
epoch: 1
release: 162.ep
summary: Mark modules as loaded or unloaded
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Module-Loaded-0.06-162.ep.noarch.rpm
checksum_type: sha256
description:
  When testing applications, often you find yourself needing to provide
  functionality in your test environment that would usually be provided by
  external modules. Rather than munging the %INC by hand to mark these external
  modules as loaded, so they are not attempted to be loaded by perl, this module
  offers you a very simple way to mark modules as loaded and/or unloaded.


pkgId: 7eacce2a3fdf7308ff60206cc963a06860b0c5c048f84071ba4a0e3553ffe646
name: local-perl-Moo
arch: noarch
version: 0.009012
epoch: 0
release: 1
summary: Moo - Minimalist Object Orientation (with Moose compatiblity)
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: S Trout cpanMSTROUT <mst@shadowcat.co.uk>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Moo-0.009012-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Moo-0.009012-1.noarch.rpm
checksum_type: sha256
description:
  This module is an extremely light-weight, high-performance L<Moose> replacement.
  It also avoids depending on any XS modules to allow simple deployments.  The
  name C<Moo> is based on the idea that it provides almost -but not quite- two
  thirds of L<Moose>.

  Unlike C<Mouse> this module does not aim at full L<Moose> compatibility.  See
  L</INCOMPATIBILITIES> for more details.


pkgId: fdb40d1d491c375c9fecf07b9cc9834910f94b248cdf973c7fd700971fede182
name: local-perl-Moose
arch: x86_64
version: 2.0401
epoch: 0
release: 1
summary: Moose - A postmodern object system for Perl 5
description: None.
url: http://www.cpan.org
rpm_license: Artistic
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Moose-2.0401-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Moose-2.0401-1.x86_64.rpm
checksum_type: sha256
rpm_vendor:
  Moose is maintained by the Moose Cabal, along with the help of many contributors. See L<Moose/CABAL> and L<Moose/CONTRIBUTORS> for details.


pkgId: 808ec285fae66da6b57618dd2e35b408470be2b227eef13ccae49cec8d64e528
name: local-perl-MooseX-Aliases
arch: noarch
version: 0.10
epoch: 0
release: 1
summary: MooseX-Aliases - easy aliasing of methods and attributes in Moose
description: None.
url: http://www.cpan.org
rpm_license: Artistic
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-MooseX-Aliases-0.10-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MooseX-Aliases-0.10-1.noarch.rpm
checksum_type: sha256
rpm_vendor:
  Jesse Luehrs <doy at tozt dot net>, Chris Prather <chris@prather.org>, Justin Hunter <justin.d.hunter at gmail dot com>


pkgId: 230ab3fcf7025024c6eeeb0d55451d2803e5b8fa153e963ebcb547328d601ffd
name: local-perl-MooseX-Role-Parameterized
arch: noarch
version: 0.27
epoch: 0
release: 1
summary: MooseX-Role-Parameterized - roles with composition parameters
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Shawn M Moore, C<sartak@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-MooseX-Role-Parameterized-0.27-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MooseX-Role-Parameterized-0.27-1.noarch.rpm
checksum_type: sha256
description:
  Your parameterized role consists of two new things: parameter declarations
  and a C<role> block.

  Parameters are declared using the L</parameter> keyword which very much
  resembles L<Moose/has>. You can use any option that L<Moose/has> accepts. The
  default value for the C<is> option is C<ro> as that's a very common case. Use
  C<< is => 'bare' >> if you want no accessor. These parameters will get their
  values when the consuming class (or role) uses L<Moose/with>. A parameter
  object will be constructed with these values, and passed to the C<role> block.

  The C<role> block then uses the usual L<Moose::Role> keywords to build up a
  role. You can shift off the parameter object to inspect what the consuming
  class provided as parameters. You use the parameters to customize your
  role however you wish.

  There are many possible implementations for parameterized roles (hopefully with
  a consistent enough API); I believe this to be the easiest and most flexible
  design. Coincidentally, Pugs originally had an eerily similar design.

  See L<MooseX::Role::Parameterized::Extending> for some tips on how to extend
  this module.


pkgId: 60564e5f4ee902de4882acc88d3c4e18c172d215a61632fe7cb7c9da35016e06
name: local-perl-Mouse
arch: x86_64
version: 0.97
epoch: 0
release: 1
summary: Mouse - Moose minus the antlers
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Shawn M Moore <sartak at gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Mouse-0.97-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mouse-0.97-1.x86_64.rpm
checksum_type: sha256
description:
  L<Moose|Moose> is a postmodern object system for Perl5. Moose is wonderful.

  Unfortunately, Moose has a compile-time penalty. Though significant progress
  has been made over the years, the compile time penalty is a non-starter for
  some very specific applications. If you are writing a command-line application
  or CGI script where startup time is essential, you may not be able to use
  Moose (we recommend that you instead use persistent Perl executing environments
  like C<FastCGI> for the latter, if possible).

  Mouse is a Moose compatible object system, which aims to alleviate this penalty
  by providing a subset of Moose's functionality.

  We're also going as light on dependencies as possible. Mouse currently has
  B<no dependencies> except for building/testing modules. Mouse also works
  without XS, although it has an XS backend to make it much faster.


pkgId: ad1a9a8e62f314f8958bca49810060243c2e712d2f201b73bbcdd37d6207d1a1
name: local-perl-Mozilla-CA
arch: noarch
version: 20110409
epoch: 0
release: 1
summary: Mozilla-CA - Mozilla's CA cert bundle in PEM format
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Mozilla-CA-20110409-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mozilla-CA-20110409-1.noarch.rpm
checksum_type: sha256
description:
  Mozilla::CA provides a copy of Mozilla's bundle of Certificate Authority
  certificates in a form that can be consumed by modules and libraries
  based on OpenSSL.

  The module provide a single function:

  =over

  =item SSL_ca_file()

  Returns the absolute path to the Mozilla's CA cert bundle PEM file.

  =back


pkgId: b23be06ccdbf315b04500c0fd4141c816729165efe9aaf602db18b6ec9747702
name: local-perl-Net-DNS
arch: x86_64
version: 0.68
epoch: 0
release: 1
summary: Net-DNS - Perl DNS resolver module
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Olaf Kolkman <olaf@net-dns.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Net-DNS-0.68-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-DNS-0.68-1.x86_64.rpm
checksum_type: sha256
description:
  Net::DNS is a collection of Perl modules that act as a Domain
  Name System (DNS) resolver.  It allows the programmer to perform
  DNS queries that are beyond the capabilities of C<gethostbyname>
  and C<gethostbyaddr>.

  The programmer should be somewhat familiar with the format of
  a DNS packet and its various sections.  See RFC 1035 or
  I<DNS and BIND> (Albitz & Liu) for details.


pkgId: 0fc4cdd317bc25be520ea5c18b0fdc254cb367563625ad0be55b98d573c3acf5
name: local-perl-Net-Daemon
arch: noarch
version: 0.48
epoch: 0
release: 1
summary: Net-Daemon - Perl extension for portable daemons
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jochen Wiedmann (joe@ispsoft.de)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Net-Daemon-0.48-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-Daemon-0.48-1.noarch.rpm
checksum_type: sha256
description:
  Net::Daemon is an abstract base class for implementing portable server
  applications in a very simple way. The module is designed for Perl 5.005
  and threads, but can work with fork() and Perl 5.004.

  The Net::Daemon class offers methods for the most common tasks a daemon
  needs: Starting up, logging, accepting clients, authorization, restricting
  its own environment for security and doing the true work. You only have to
  override those methods that aren't appropriate for you, but typically
  inheriting will safe you a lot of work anyways.


pkgId: f4c68d9fd9ff7bb16953d84b2134b21f07b8c94e175e3f608c726a81c47fb343
name: local-perl-Net-HTTP
arch: noarch
version: 6.01
epoch: 0
release: 1
summary: Net-HTTP - Low-level HTTP connection (client)
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gisle Aas <gisle@activestate.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Net-HTTP-6.01-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-HTTP-6.01-1.noarch.rpm
checksum_type: sha256
description:
  The C<Net::HTTP> class is a low-level HTTP client.  An instance of the
  C<Net::HTTP> class represents a connection to an HTTP server.  The
  HTTP protocol is described in RFC 2616.  The C<Net::HTTP> class
  supports C<HTTP/1.0> and C<HTTP/1.1>.

  C<Net::HTTP> is a sub-class of C<IO::Socket::INET>.  You can mix the
  methods described below with reading and writing from the socket
  directly.  This is not necessary a good idea, unless you know what you
  are doing.

  The following methods are provided (in addition to those of
  C<IO::Socket::INET>):

  =over

  =item $s = Net::HTTP->new( %options )

  The C<Net::HTTP> constructor method takes the same options as
  C<IO::Socket::INET>'s as well as these:

    Host:            Initial host attribute value
    KeepAlive:       Initial keep_alive attribute value
    SendTE:          Initial send_te attribute_value
    HTTPVersion:     Initial http_version attribute value
    PeerHTTPVersion: Initial peer_http_version attribute value
    MaxLineLength:   Initial max_line_length attribute value
    MaxHeaderLines:  Initial max_header_lines attribute value

  The C<Host> option is also the default for C<IO::Socket::INET>'s
  C<PeerAddr>.  The C<PeerPort> defaults to 80 if not provided.

  The C<Listen> option provided by C<IO::Socket::INET>'s constructor
  method is not allowed.

  If unable to connect to the given HTTP server then the constructor
  returns C<undef> and $@ contains the reason.  After a successful
  connect, a C<Net:HTTP> object is returned.

  =item $s->host

  Get/set the default value of the C<Host> header to send.  The $host
  must not be set to an empty string (or C<undef>) for HTTP/1.1.

  =item $s->keep_alive

  Get/set the I<keep-alive> value.  If this value is TRUE then the
  request will be sent with headers indicating that the server should try
  to keep the connection open so that multiple requests can be sent.

  The actual headers set will depend on the value of the C<http_version>
  and C<peer_http_version> attributes.

  =item $s->send_te

  Get/set the a value indicating if the request will be sent with a "TE"
  header to indicate the transfer encodings that the server can choose to
  use.  The list of encodings announced as accepted by this client depends
  on availability of the following modules: C<Compress::Raw::Zlib> for
  I<deflate>, and C<IO::Compress::Gunzip> for I<gzip>.

  =item $s->http_version

  Get/set the HTTP version number that this client should announce.
  This value can only be set to "1.0" or "1.1".  The default is "1.1".

  =item $s->peer_http_version

  Get/set the protocol version number of our peer.  This value will
  initially be "1.0", but will be updated by a successful
  read_response_headers() method call.

  =item $s->max_line_length

  Get/set a limit on the length of response line and response header
  lines.  The default is 8192.  A value of 0 means no limit.

  =item $s->max_header_length

  Get/set a limit on the number of header lines that a response can
  have.  The default is 128.  A value of 0 means no limit.

  =item $s->format_request($method, $uri, %headers, [$content])

  Format a request message and return it as a string.  If the headers do
  not include a C<Host> header, then a header is inserted with the value
  of the C<host> attribute.  Headers like C<Connection> and
  C<Keep-Alive> might also be added depending on the status of the
  C<keep_alive> attribute.

  If $content is given (and it is non-empty), then a C<Content-Length>
  header is automatically added unless it was already present.

  =item $s->write_request($method, $uri, %headers, [$content])

  Format and send a request message.  Arguments are the same as for
  format_request().  Returns true if successful.

  =item $s->format_chunk( $data )

  Returns the string to be written for the given chunk of data.

  =item $s->write_chunk($data)

  Will write a new chunk of request entity body data.  This method
  should only be used if the C<Transfer-Encoding> header with a value of
  C<chunked> was sent in the request.  Note, writing zero-length data is
  a no-op.  Use the write_chunk_eof() method to signal end of entity
  body data.

  Returns true if successful.

  =item $s->format_chunk_eof( %trailers )

  Returns the string to be written for signaling EOF when a
  C<Transfer-Encoding> of C<chunked> is used.

  =item $s->write_chunk_eof( %trailers )

  Will write eof marker for chunked data and optional trailers.  Note
  that trailers should not really be used unless is was signaled
  with a C<Trailer> header.

  Returns true if successful.

  =item ($code, $mess, %headers) = $s->read_response_headers( %opts )

  Read response headers from server and return it.  The $code is the 3
  digit HTTP status code (see L<HTTP::Status>) and $mess is the textual
  message that came with it.  Headers are then returned as key/value
  pairs.  Since key letter casing is not normalized and the same key can
  even occur multiple times, assigning these values directly to a hash
  is not wise.  Only the $code is returned if this method is called in
  scalar context.

  As a side effect this method updates the 'peer_http_version'
  attribute.

  Options might be passed in as key/value pairs.  There are currently
  only two options supported; C<laxed> and C<junk_out>.

  The C<laxed> option will make read_response_headers() more forgiving
  towards servers that have not learned how to speak HTTP properly.  The
  C<laxed> option is a boolean flag, and is enabled by passing in a TRUE
  value.  The C<junk_out> option can be used to capture bad header lines
  when C<laxed> is enabled.  The value should be an array reference.
  Bad header lines will be pushed onto the array.

  The C<laxed> option must be specified in order to communicate with
  pre-HTTP/1.0 servers that don't describe the response outcome or the
  data they send back with a header block.  For these servers
  peer_http_version is set to "0.9" and this method returns (200,
  "Assumed OK").

  The method will raise an exception (die) if the server does not speak
  proper HTTP or if the C<max_line_length> or C<max_header_length>
  limits are reached.  If the C<laxed> option is turned on and
  C<max_line_length> and C<max_header_length> checks are turned off,
  then no exception will be raised and this method will always
  return a response code.

  =item $n = $s->read_entity_body($buf, $size);

  Reads chunks of the entity body content.  Basically the same interface
  as for read() and sysread(), but the buffer offset argument is not
  supported yet.  This method should only be called after a successful
  read_response_headers() call.

  The return value will be C<undef> on read errors, 0 on EOF, -1 if no data
  could be returned this time, otherwise the number of bytes assigned
  to $buf.  The $buf is set to "" when the return value is -1.

  You normally want to retry this call if this function returns either
  -1 or C<undef> with C<$!> as EINTR or EAGAIN (see L<Errno>).  EINTR
  can happen if the application catches signals and EAGAIN can happen if
  you made the socket non-blocking.

  This method will raise exceptions (die) if the server does not speak
  proper HTTP.  This can only happen when reading chunked data.

  =item %headers = $s->get_trailers

  After read_entity_body() has returned 0 to indicate end of the entity
  body, you might call this method to pick up any trailers.

  =item $s->_rbuf

  Get/set the read buffer content.  The read_response_headers() and
  read_entity_body() methods use an internal buffer which they will look
  for data before they actually sysread more from the socket itself.  If
  they read too much, the remaining data will be left in this buffer.

  =item $s->_rbuf_length

  Returns the number of bytes in the read buffer.  This should always be
  the same as:

      length($s->_rbuf)

  but might be more efficient.

  =back


pkgId: 6c45722f61c34e97f0865b2a80a9ad9b2b31985c1f0e7d0d4567c55b3307989d
name: local-perl-Net-HTTPS-Any
arch: noarch
version: 0.10
epoch: 0
release: 1
summary: Net-HTTPS-Any - Simple HTTPS class using whichever underlying SSL module is available
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ivan Kohler <ivan-net-https-any@freeside.biz>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Net-HTTPS-Any-0.10-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-HTTPS-Any-0.10-1.noarch.rpm
checksum_type: sha256
description:
  This is a simple wrapper around either of the two available SSL
  modules.  It offers a unified API for sending GET and POST requests over HTTPS
  and receiving responses.

  It depends on Net::SSLeay _or_ ( Crypt::SSLeay and LWP::UserAgent ).


pkgId: ec3a9ed0017e51a88cb65a15527a03f6907f769121622d0483bd0aa04995ff95
name: local-perl-Net-SMTP-SSL
arch: noarch
version: 1.01
epoch: 0
release: 1
summary: Net-SMTP-SSL - SSL support for Net::SMTP
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Casey West <casey@geeknest.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Net-SMTP-SSL-1.01-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-SMTP-SSL-1.01-1.noarch.rpm
checksum_type: sha256
description:
  Implements the same API as L<Net::SMTP|Net::SMTP>, but uses
  L<IO::Socket::SSL|IO::Socket::SSL> for its network operations. Due to
  the nature of C<Net::SMTP>'s C<new> method, it is not overridden to make
  use of a default port for the SMTPS service. Perhaps future versions
  will be smart like that. Port C<465> is usually what you want, and it's
  not a pain to specify that.

  For interface documentation, please see L<Net::SMTP|Net::SMTP>.


pkgId: 976a56455360dda0537ac9897377875fab4f589adeea6fcbe91339d5fe212f38
name: local-perl-Net-Server
arch: noarch
version: 2.006
epoch: 0
release: 1
summary: Net-Server - Extensible, general Perl server engine
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Paul Seamons (paul@seamons.com) and Rob Brown (bbb@cpan.org)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Net-Server-2.006-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-Server-2.006-1.noarch.rpm
checksum_type: sha256
description:
  C<Net::Server> is an extensible, generic Perl server engine.

  C<Net::Server> attempts to be a generic server as in C<Net::Daemon>
  and C<NetServer::Generic>.  It includes with it the ability to run as
  an inetd process (C<Net::Server::INET>), a single connection server
  (C<Net::Server> or C<Net::Server::Single>), a forking server
  (C<Net::Server::Fork>), a preforking server which maintains a constant
  number of preforked children (C<Net::Server::PreForkSimple>), or as a
  managed preforking server which maintains the number of children based
  on server load (C<Net::Server::PreFork>).  In all but the inetd type,
  the server provides the ability to connect to one or to multiple
  server ports.

  The additional server types are made possible via "personalities" or
  sub classes of the C<Net::Server>.  By moving the multiple types of
  servers out of the main C<Net::Server> class, the C<Net::Server>
  concept is easily extended to other types (in the near future, we
  would like to add a "Thread" personality).

  C<Net::Server> borrows several concepts from the Apache Webserver.
  C<Net::Server> uses "hooks" to allow custom servers such as SMTP,
  HTTP, POP3, etc. to be layered over the base C<Net::Server> class.  In
  addition the C<Net::Server::PreFork> class borrows concepts of
  min_start_servers, max_servers, and min_waiting servers.
  C<Net::Server::PreFork> also uses the concept of an flock serialized
  accept when accepting on multiple ports (PreFork can choose between
  flock, IPC::Semaphore, and pipe to control serialization).


pkgId: 240d0737dcc94163b729c6d2cc5685f56e54093fef447693e8a8f4a3b3bec91a
name: local-perl-Net-Twitter
arch: noarch
version: 3.18001
epoch: 0
release: 1
summary: Net-Twitter - A perl interface to the Twitter API
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Marc Mims <marc@questright.com> (@semifor on Twitter)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Net-Twitter-3.18001-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-Twitter-3.18001-1.noarch.rpm
checksum_type: sha256
description:
  This module implements the core features of C<Net::Twitter>.  See L<Net::Twitter> for full documentation.

  Although this module can be used directly, you are encouraged to use C<Net::Twitter> instead.


pkgId: f5e5374608cfe69da8dc300bb9bc6afc6eafeb50e83deb9870e2a4640c832d3a
name: local-perl-Number-Compare
arch: noarch
version: 0.03
epoch: 0
release: 1
summary: Number-Compare - numeric comparisons
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Richard Clamp <richardc@unixbeard.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Number-Compare-0.03-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Number-Compare-0.03-1.noarch.rpm
checksum_type: sha256
description:
  Number::Compare compiles a simple comparison to an anonymous
  subroutine, which you can call with a value to be tested again.

  Now this would be very pointless, if Number::Compare didn't understand
  magnitudes.

  The target value may use magnitudes of kilobytes (C<k>, C<ki>),
  megabytes (C<m>, C<mi>), or gigabytes (C<g>, C<gi>).  Those suffixed
  with an C<i> use the appropriate 2**n version in accordance with the
  IEC standard: http://physics.nist.gov/cuu/Units/binary.html


pkgId: f57a5a136d6e0e9e088de1cb6bbca2d85ac8e65e7ba3b030fa836f8776fd2f19
name: local-perl-Number-Spell
arch: noarch
version: 0.04
epoch: 0
release: 1
summary: Number-Spell - Perl extension for spelling out numbers
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Les Howard <les@lesandchris.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Number-Spell-0.04-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Number-Spell-0.04-1.noarch.rpm
checksum_type: sha256
description:
  Number::Spell provides functionality for spelling out numbers.  Currently only
  integers are supported.

  By default Number::Spell does American formatting, but can be configured
  to do European formatting by calling it with the "Format => 'eu'" option:

  	spell_number( ...  , Format => 'eu');

  American and European formatting differ in how they represent numbers one
  billion and above.

  	number 		:  	20000000000 (2 * 10^11)
  	American format :	twenty billion
  	European format :	twenty thousand million

  With American formatting (default) Number::Spell should work for integers to

  	nine hundred ninety nine vigintillion nine hundred ninety nine
  	novemdecillion nine hundred ninety nine octodecillion nine hundred
  	ninety nine septendecillion nine hundred ninety nine sexdecillion nine
  	hundred ninety nine quindecillion nine hundred ninety nine
  	quattuordecillion nine hundred ninety nine tredecillion nine hundred
  	ninety nine duodecillion nine hundred ninety nine undecillion nine
  	hundred ninety nine decillion nine hundred ninety nine nonillion nine
  	hundred ninety nine octillion nine hundred ninety nine septillion nine
  	hundred ninety nine sextillion nine hundred ninety nine quintillion nine
  	hundred ninety nine quadrillion nine hundred ninety nine trillion nine
  	hundred ninety nine billion nine hundred ninety nine million nine
  	hundred ninety nine thousand nine hundred ninety nine

  and in European formatting mode is should be valid up-to

  	nine hundred ninety nine thousand nine hundred ninety nine vigintillion
  	nine hundred ninety nine thousand nine hundred ninety nine
  	novemdecillion nine hundred ninety nine thousand nine hundred ninety
  	nine octodecillion nine hundred ninety nine thousand nine hundred
  	ninety nine septendecillion nine hundred ninety nine thousand nine
  	hundred ninety nine sexdecillion nine hundred ninety nine thousand nine
  	hundred ninety nine quindecillion nine hundred ninety nine thousand
  	nine hundred ninety nine quattuordecillion nine hundred ninety nine
  	thousand nine hundred ninety nine tredecillion nine hundred ninety nine
  	thousand nine hundred ninety nine duodecillion nine hundred ninety nine
  	thousand nine hundred ninety nine undecillion nine hundred ninety nine
  	thousand nine hundred ninety nine decillion nine hundred ninety nine
  	thousand nine hundred ninety nine nonillion nine hundred ninety nine
  	thousand nine hundred ninety nine octillion nine hundred ninety nine
  	thousand nine hundred ninety nine septillion nine hundred ninety nine
  	thousand nine hundred ninety nine sextillion nine hundred ninety nine
  	thousand nine hundred ninety nine quintillion nine hundred ninety nine
  	thousand nine hundred ninety nine quadrillion nine hundred ninety nine
  	thousand nine hundred ninety nine trillion nine hundred ninety nine
  	thousand nine hundred ninety nine billion nine hundred ninety nine
  	thousand nine hundred ninety nine million nine hundred ninety nine
  	thousand nine hundred ninety nine


pkgId: 6ad0b6f72919a46865793c616255f9596765dcaf2b794b5e32051501f4a49444
name: local-perl-OLE-Storage_Lite
arch: noarch
version: 0.19
epoch: 0
release: 1
summary: OLE-Storage_Lite - Read and write OLE storage files.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Kawai Takanori (kwitknr@cpan.org)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-OLE-Storage_Lite-0.19-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-OLE-Storage_Lite-0.19-1.noarch.rpm
checksum_type: sha256
description:
  OLE::Storage_Lite allows you to read and write an OLE structured file.

  OLE::Storage_Lite::PPS is a class representing PPS. OLE::Storage_Lite::PPS::Root, OLE::Storage_Lite::PPS::File and OLE::Storage_Lite::PPS::Dir
  are subclasses of OLE::Storage_Lite::PPS.


pkgId: ce49e922a29fb628d48ad54b8b4fd54252fee16a50b7485528111d590566a018
name: local-perl-Object-Accessor
arch: noarch
version: 0.38
epoch: 1
release: 162.ep
summary: Perl module that allows per object accessors
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Object-Accessor-0.38-162.ep.noarch.rpm
checksum_type: sha256
description:
  Object::Accessor provides an interface to create per object accessors (as
  opposed to per Class accessors, as, for example, Class::Accessor provides).


pkgId: 22aae66272f49d2df07520c488344454d1fb2137e5748e30257c232a2a9dfbad
name: local-perl-PDF-EasyPDF
arch: noarch
version: 0.04
epoch: 0
release: 1
summary: PDF-EasyPDF - PDF creation from a one-file module, with postscript-like controls
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Mark Howe <mark@localdomain>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-PDF-EasyPDF-0.04-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-PDF-EasyPDF-0.04-1.noarch.rpm
checksum_type: sha256
description:
  This module started life as a workaround, on discovering that PDF::API2 and friends are extremely tricky to compile using Activestate's PerlApp utility because of the large number of runtime modules and resource files they use. The module consists of a single .pm file. It produces small PDF files, partly because it only uses the 14 standard PDF fonts. Page content is implemented using a single stream object, and the controls are vaguely postscript-like.


pkgId: 832deddf8509043e4cb9b538f630afee56ca7905ef1d39008fabbb72d9be2e29
name: local-perl-Package-Constants
arch: noarch
version: 0.02
epoch: 1
release: 162.ep
summary: List all constants declared in a package
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Package-Constants-0.02-162.ep.noarch.rpm
checksum_type: sha256
description:
  Package::Constants lists all the constants defined in a certain package.  This
  can be useful for, among others, setting up an autogenerated @EXPORT/@EXPORT_OK
  for a Constants.pm file.


pkgId: 6276c652797d754dd70c7d7477492e2ee84a80742632b2c088aceff8ffe90a61
name: local-perl-PadWalker
arch: x86_64
version: 1.92
epoch: 0
release: 1
summary: PadWalker - play with other peoples' lexical variables
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Robin Houston <robin@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-PadWalker-1.92-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-PadWalker-1.92-1.x86_64.rpm
checksum_type: sha256
description:
  PadWalker is a module which allows you to inspect (and even change!)
  lexical variables in any subroutine which called you. It will only
  show those variables which are in scope at the point of the call.

  PadWalker is particularly useful for debugging. It's even
  used by Perl's built-in debugger. (It can also be used
  for evil, of course.)

  I wouldn't recommend using PadWalker directly in production
  code, but it's your call. Some of the modules that use
  PadWalker internally are certainly safe for and useful
  in production.

  =over 4

  =item peek_my LEVEL

  =item peek_our LEVEL

  The LEVEL argument is interpreted just like the argument to C<caller>.
  So C<peek_my(0)> returns a reference to a hash of all the C<my>
  variables that are currently in scope;
  C<peek_my(1)> returns a reference to a hash of all the C<my>
  variables that are in scope at the point where the current
  sub was called, and so on.

  C<peek_our> works in the same way, except that it lists
  the C<our> variables rather than the C<my> variables.

  The hash associates each variable name with a reference
  to its value. The variable names include the sigil, so
  the variable $x is represented by the string '$x'.

  For example:

    my $x = 12;
    my $h = peek_my (0);
    ${$h->{'$x'}}++;

    print $x;  # prints 13

  Or a more complex example:

    sub increment_my_x {
      my $h = peek_my (1);
      ${$h->{'$x'}}++;
    }

    my $x=5;
    increment_my_x;
    print $x;  # prints 6

  =item peek_sub SUB

  The C<peek_sub> routine takes a coderef as its argument, and returns a hash
  of the C<my> variables used in that sub. The values will usually be undefined
  unless the sub is in use (i.e. in the call-chain) at the time. On the other
  hand:

    my $x = "Hello!";
    my $r = peek_sub(sub {$x})->{'$x'};
    print "$$r\n";	# prints 'Hello!'

  If the sub defines several C<my> variables with the same name, you'll get the
  last one. I don't know of any use for C<peek_sub> that isn't broken as a result
  of this, and it will probably be deprecated in a future version in favour of
  some alternative interface.

  =item closed_over SUB

  C<closed_over> is similar to C<peek_sub>, except that it only lists
  the C<my> variables which are used in the subroutine but defined outside:
  in other words, the variables which it closes over. This I<does> have
  reasonable uses: see L<Data::Dump::Streamer>, for example (a future version
  of which may in fact use C<closed_over>).

  =item set_closed_over SUB, HASH_REF

  C<set_closed_over> reassigns the pad variables that are closed over by the subroutine.

  The second argument is a hash of references, much like the one returned from C<closed_over>.

  =item var_name LEVEL, VAR_REF

  =item var_name SUB,   VAR_REF

  C<var_name(sub, var_ref)> returns the name of the variable referred to
  by C<var_ref>, provided it is a C<my> variable used in the sub. The C<sub>
  parameter can be either a CODE reference or a number. If it's a number,
  it's treated the same way as the argument to C<peek_my>.

  For example,

    my $foo;
    print var_name(0, \$foo);    # prints '$foo'

    sub my_name {
      return var_name(1, shift);
    }
    print my_name(\$foo);        # ditto

  =back


pkgId: d61f6e72c37ddb0e407c4553393e49ac4eceb96c1e6631cbc9df3aafd7ac8e5e
name: local-perl-Params-Util
arch: x86_64
version: 1.04
epoch: 0
release: 1
summary: Params-Util - Simple, compact and correct param-checking functions
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Adam Kennedy <adamk@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Params-Util-1.04-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Params-Util-1.04-1.x86_64.rpm
checksum_type: sha256
description:
  C<Params::Util> provides a basic set of importable functions that makes
  checking parameters a hell of a lot easier

  While they can be (and are) used in other contexts, the main point
  behind this module is that the functions B<both> Do What You Mean,
  and Do The Right Thing, so they are most useful when you are getting
  params passed into your code from someone and/or somewhere else
  and you can't really trust the quality.

  Thus, C<Params::Util> is of most use at the edges of your API, where
  params and data are coming in from outside your code.

  The functions provided by C<Params::Util> check in the most strictly
  correct manner known, are documented as thoroughly as possible so their
  exact behaviour is clear, and heavily tested so make sure they are not
  fooled by weird data and Really Bad Things.

  To use, simply load the module providing the functions you want to use
  as arguments (as shown in the SYNOPSIS).

  To aid in maintainability, C<Params::Util> will B<never> export by
  default.

  You must explicitly name the functions you want to export, or use the
  C<:ALL> param to just have it export everything (although this is not
  recommended if you have any _FOO functions yourself with which future
  additions to C<Params::Util> may clash)


pkgId: 054d79428d71b2ad6bab811085a71dd3bea3e0110066e62fb4cff20280e6db8e
name: local-perl-PathTools
arch: x86_64
version: 3.47
epoch: 0
release: 1
summary: PathTools - get pathname of current working directory
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: by Ken Williams <KWILLIAMS@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-PathTools-3.47-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-PathTools-3.47-1.x86_64.rpm
checksum_type: sha256
description:
  This module provides functions for determining the pathname of the
  current working directory.  It is recommended that getcwd (or another
  *cwd() function) be used in I<all> code to ensure portability.

  By default, it exports the functions cwd(), getcwd(), fastcwd(), and
  fastgetcwd() (and, on Win32, getdcwd()) into the caller's namespace.


pkgId: 9e7d27a9daf01083f9f9c1730034cb17796f378c5211a7986b1fc9bccf698d96
name: local-perl-PlRPC
arch: noarch
version: 0.2020
epoch: 0
release: 1
summary: PlRPC - Perl Remote Method Invocation
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jochen Wiedmann (jochen.wiedmann@freenet.de)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-PlRPC-0.2020-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-PlRPC-0.2020-1.noarch.rpm
checksum_type: sha256
description:
  PlRPC (Perl RPC) is a package for implementing servers and clients that
  are written in Perl entirely. The name is borrowed from Sun's RPC
  (Remote Procedure Call), but it could as well be RMI like Java's "Remote
  Method Interface), because PlRPC gives you the complete power of Perl's
  OO framework in a very simple manner.

  RPC::PlServer is the package used on the server side, and you guess what
  RPC::PlClient is for. Both share the package RPC::PlServer::Comm for
  communication purposes. See L<PlRPC::Client(3)> and L<RPC::PlServer::Comm>
  for these parts.

  PlRPC works by defining a set of methods that may be executed by the client.
  For example, the server might offer a method "multiply" to the client. Now
  the clients method call

      @result = $client->multiply($a, $b);

  will be immediately mapped to a method call

      @result = $server->multiply($a, $b);

  on the server. The arguments and results will be transferred to or from
  the server automagically. (This magic has a name in Perl: It's the
  Storable module, my thanks to Raphael Manfredi for this excellent
  package.) Simple, eh? :-)

  The RPC::PlServer and RPC::PlClient are abstract servers and clients: You
  have to derive your own classes from it.


pkgId: b190eeb7f50ffd358c9af8101233a4f9205a1373d4a4895d7f5d0e3acca31d41
name: local-perl-Plack
arch: noarch
version: 0.9985
epoch: 0
release: 1
summary: Plack - Perl Superglue for Web frameworks and Web Servers (PSGI toolkit)
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tatsuhiko Miyagawa
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Plack-0.9985-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Plack-0.9985-1.noarch.rpm
checksum_type: sha256
description:
  Plack is a set of tools for using the PSGI stack. It contains
  middleware components, a reference server and utilities for Web
  application frameworks. Plack is like Ruby's Rack or Python's Paste
  for WSGI.

  See L<PSGI> for the PSGI specification and L<PSGI::FAQ> to know what
  PSGI and Plack are and why we need them.


pkgId: 6a386e4bad2d6c528259aa906089d5220f80f50353ec895f0a07b4b7ca8afc80
name: local-perl-Pod-Escapes
arch: noarch
version: 1.04
epoch: 1
release: 162.ep
summary: Perl module for resolving POD escape sequences
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Pod-Escapes-1.04-162.ep.noarch.rpm
checksum_type: sha256
description:
  This module provides things that are useful in decoding Pod E<...> sequences.
  Presumably, it should be used only by Pod parsers and/or formatters.


pkgId: bd5a5dee7db03c8b19cae78e49830fd81cb43ccdd1e9a70a9d1ef50c19743475
name: local-perl-Pod-Simple
arch: noarch
version: 3.16
epoch: 1
release: 162.ep
summary: Framework for parsing POD documentation
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Pod-Simple-3.16-162.ep.noarch.rpm
checksum_type: sha256
description:
  Pod::Simple is a Perl library for parsing text in the Pod ("plain old
  documentation") markup language that is typically used for writing
  documentation for Perl and for Perl modules.


pkgId: ae79685c5c62713e00b1a43b6b7a915305c2d18a1a9443e3a767a59a4af02a35
name: local-perl-Readonly
arch: noarch
version: 1.03
epoch: 0
release: 1
summary: Readonly - Facility for creating read-only scalars, arrays, hashes.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Eric J. Roode <roode@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Readonly-1.03-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Readonly-1.03-1.noarch.rpm
checksum_type: sha256
description:
  This is a facility for creating non-modifiable variables.  This is
  useful for configuration files, headers, etc.  It can also be useful
  as a development and debugging tool, for catching updates to variables
  that should not be changed.

  If any of the values you pass to C<Scalar>, C<Array>, or C<Hash> are
  references, then those functions recurse over the data structures,
  marking everything as Readonly.  Usually, this is what you want: the
  entire structure nonmodifiable.  If you want only the top level to be
  Readonly, use the alternate C<Scalar1>, C<Array1> and C<Hash1>
  functions.

  Please note that most users of Readonly will also want to install a
  companion module Readonly::XS.  See the L</CONS> section below for more
  details.


pkgId: f1a4b498bea733fde878881ecb5e8e2325018210225bbb303aff210c7796928a
name: local-perl-Regexp-Common
arch: noarch
version: 2011121001
epoch: 0
release: 1
summary: Regexp-Common - Provide commonly requested regular expressions
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Abigail <regexp-common@abigail.be>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Regexp-Common-2011121001-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Regexp-Common-2011121001-1.noarch.rpm
checksum_type: sha256
description:
  By default, this module exports a single hash (C<%RE>) that stores or generates
  commonly needed regular expressions (see L<"List of available patterns">).

  There is an alternative, subroutine-based syntax described in
  L<"Subroutine-based interface">.


pkgId: 4f281c7f50b76a32a28d141030fd9f77d1b9b933b16bc138ba47f72f9ffd1d0f
name: local-perl-Regexp-IPv6
arch: noarch
version: 0.03
epoch: 0
release: 1
summary: Regexp-IPv6 - Regular expression for IPv6 addresses
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Salvador Fandino <sfandino@yahoo.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Regexp-IPv6-0.03-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Regexp-IPv6-0.03-1.noarch.rpm
checksum_type: sha256
description:
  This module exports the $IPv6_re regular expression that matches any
  valid IPv6 address as described in "RFC 2373 - 2.2 Text Representation
  of Addresses" but C<::>. Any string not compliant with such RFC will
  be rejected.

  To match full strings use C</^$IPv6_re$/>.


pkgId: d55135ee4606d09178082928e38d133fa66bc735959c1ccfaa50a8701febed1c
name: local-perl-Return-Value
arch: noarch
version: 1.666001
epoch: 0
release: 1
summary: Return-Value - Polymorphic Return Values
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Casey West <casey@geeknest.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Return-Value-1.666001-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Return-Value-1.666001-1.noarch.rpm
checksum_type: sha256
description:
  Polymorphic return values are a horrible idea, but this library was written
  based on the notion that they were useful.  Often, we just want to know if
  something worked or not.  Other times, we'd like to know what the error text
  was.  Still others, we may want to know what the error code was, and what the
  error properties were.  We don't want to handle objects or data structures for
  every single return value, but we do want to check error conditions in our code
  because that's what good programmers do.

  When functions are successful they may return true, or perhaps some useful
  data.  In the quest to provide consistent return values, this gets confusing
  between complex, informational errors and successful return values.

  This module provides these features with a simplistic API that should get you
  what you're looking for in each context a return value is used in.


pkgId: 1f7bab1beab551408a98f4bc8e58744e9ff770262f06fdc66efb6035a82454cf
name: local-perl-SOAP-Lite
arch: noarch
version: 0.712
epoch: 0
release: 1
summary: SOAP-Lite - Perl's Web Services Toolkit
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Pavel Kulchenko, Randy J Ray, Byrne Reese, Martin Kutter (MKUTTER@cpan.org)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-SOAP-Lite-0.712-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-SOAP-Lite-0.712-1.noarch.rpm
checksum_type: sha256
description:
  SOAP::Lite is a collection of Perl modules which provides a simple and
  lightweight interface to the Simple Object Access Protocol (SOAP) both on
  client and server side.


pkgId: 425e092293a76f17a5aa22a5db7d17f056ac653ef1e85d66cb17a4bfc68ca534
name: local-perl-SQL-Statement
arch: noarch
version: 1.400
epoch: 0
release: 1
summary: SQL-Statement - SQL parsing and processing engine
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jeff Zucker <jeff@vpservices.com>, Jens Rehsack <rehsack@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-SQL-Statement-1.400-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-SQL-Statement-1.400-1.noarch.rpm
checksum_type: sha256
description:
  The SQL::Statement module implements a pure Perl SQL parsing and execution
  engine. While it by no means implements full ANSI standard, it does support
  many features including column and table aliases, built-in and user-defined
  functions, implicit and explicit joins, complex nested search conditions,
  and other features.

  SQL::Statement is a small embeddable Database Management System
  (DBMS). This means that it provides all of the services of a simple
  DBMS except that instead of a persistent storage mechanism, it has two
  things: 1) an in-memory storage mechanism that allows you to prepare,
  execute, and fetch from SQL statements using temporary tables and 2) a
  set of software sockets where any author can plug in any storage
  mechanism.

  There are three main uses for SQL::Statement. One or another (hopefully not
  all) may be irrelevant for your needs: 1) to access and manipulate data in
  CSV, XML, and other formats 2) to build your own DBD for a new data source
  3) to parse and examine the structure of SQL statements.


pkgId: 39065ce999da97c5276c4375deeb89dddb4d7b2ad92ba4d2f09d954d3adcffe7
name: local-perl-Scalar-List-Utils
arch: x86_64
version: 1.23
epoch: 0
release: 162.ep
summary: A selection of general-utility scalar and list subroutines
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Scalar-List-Utils-1.23-162.ep.x86_64.rpm
checksum_type: sha256
description:
  Scalar::Util and List::Util contain a selection of subroutines that people have
  expressed would be nice to have in the perl core, but the usage would not
  really be high enough to warrant the use of a keyword, and the size so small
  such that being individual extensions would be wasteful.


pkgId: 63fdfa7b9772425c057102cdf7219c66c02aeef915714c812aa2613a5cc2cb97
name: local-perl-Set-Crontab
arch: noarch
version: 1.03
epoch: 0
release: 1
summary: Set-Crontab - Expand crontab(5)-style integer lists
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: ams@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Set-Crontab-1.03-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Set-Crontab-1.03-1.noarch.rpm
checksum_type: sha256
description:
  Set::Crontab parses crontab-style lists of integers and defines some
  utility functions to make it easier to deal with them.


pkgId: e6ebcf18743235f5e618d4edee3095779bf1db42d605dd0878bc4b827ab2e08d
name: local-perl-Set-IntSpan
arch: noarch
version: 1.16
epoch: 0
release: 1
summary: Set-IntSpan - Manages sets of integers, newsrc style
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Steven McDougall (swmcd@world.std.com)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Set-IntSpan-1.16-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Set-IntSpan-1.16-1.noarch.rpm
checksum_type: sha256
description:
  C<Set::IntSpan> manages sets of integers.
  It is optimized for sets that have long runs of consecutive integers.
  These arise, for example, in .newsrc files, which maintain lists of articles:

    alt.foo: 1-21,28,31
    alt.bar: 1-14192,14194,14196-14221

  A run of consecutive integers is sometimes called a I<span>.

  Sets are stored internally in a run-length coded form.
  This provides for both compact storage and efficient computation.
  In particular,
  set operations can be performed directly on the encoded representation.

  C<Set::IntSpan> is designed to manage finite sets.
  However, it can also represent some simple infinite sets, such as { x | x>n }.
  This allows operations involving complements to be carried out consistently,
  without having to worry about the actual value of INT_MAX on your machine.


pkgId: 8040eb7e89fd5d7d4e1981fdf1a6abba4e6f256ca3c68f4303864d9ffc17b98a
name: local-perl-Socket6
arch: x86_64
version: 0.23
epoch: 0
release: 1
summary: Socket6 - IPv6 related part of the C socket.h defines and structure manipulators
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: umemoto@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Socket6-0.23-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Socket6-0.23-1.x86_64.rpm
checksum_type: sha256
description:
  This module provides glue routines to the various IPv6 functions.

  If you use the Socket6 module,
  be sure to specify "use Socket" as well as "use Socket6".

  Functions supplied are:

  =item inet_pton FAMILY, TEXT_ADDRESS

      This function takes an IP address in presentation (or string) format
      and converts it into numeric (or binary) format.
      The type of IP address conversion (IPv4 versus IPv6) is controlled
      by the FAMILY argument.

  =item inet_ntop FAMILY, BINARY_ADDRESS

      This function takes an IP address in numeric (or binary) format
      and converts it into presentation (or string) format
      The type of IP address conversion (IPv4 versus IPv6) is controlled
      by the FAMILY argument.

  =item pack_sockaddr_in6 PORT, ADDR

      This function takes two arguments: a port number, and a 16-octet
      IPv6 address structure (as returned by inet_pton()).
      It returns the sockaddr_in6 structure with these arguments packed
      into their correct fields, as well as the AF_INET6 family.
      The other fields are not set and their values should not be relied upon.

  =item pack_sockaddr_in6_all PORT, FLOWINFO, ADDR, SCOPEID

      This function takes four arguments: a port number, a 16-octet
      IPv6 address structure (as returned by inet_pton), any
      special flow information, and any specific scope information.
      It returns a complete sockaddr_in6 structure with these arguments packed
      into their correct fields, as well as the AF_INET6 family.

  =item unpack_sockaddr_in6 NAME

      This function takes a sockaddr_in6 structure (as returned by
      pack_sockaddr_in6()) and returns a list of of two elements:
      the port number and the 16-octet IP address.
      This function will croak if it determines it has not been
      passed an IPv6 structure.

  =item unpack_sockaddr_in6_all NAME

      This function takes a sockaddr_in6 structure (as returned by
      pack_sockaddr_in6()) and returns a list of of four elements:
      the port number, the flow information, the 16-octet IP address,
      and the scope information.
      This function will croak if it determines it has not been
      passed an IPv6 structure.

  =item gethostbyname2 HOSTNAME, FAMILY

  =item getaddrinfo NODENAME, SERVICENAME, [FAMILY, SOCKTYPE, PROTOCOL, FLAGS]

      This function converts node names to addresses and service names
      to port numbers.
      If the NODENAME argument is not a false value,
      then a nodename to address lookup is performed;
      otherwise a service name to port number lookup is performed.
      At least one of NODENAME and SERVICENAME must have a true value.

      If the lookup is successful, a list consisting of multiples of
      five elements is returned.
      Each group of five elements consists of the address family,
      socket type, protocol, 16-octet IP address, and the canonical
      name (undef if the node name passed is already the canonical name).

      The arguments FAMILY, SOCKTYPE, PROTOCOL, and FLAGS are all optional.

      This function will croak if it determines it has not been
      passed an IPv6 structure.

      If the lookup is unsuccessful, the function returns a single scalar.
      This will contain the string version of that error in string context,
      and the numeric value in numeric context.

  =item getnameinfo NAME, [FLAGS]

      This function takes a socket address structure. If successful, it returns
      two strings containing the node name and service name.

      The optional FLAGS argument controls what kind of lookup is performed.

      If the lookup is unsuccessful, the function returns a single scalar.
      This will contain the string version of that error in string context,
      and the numeric value in numeric context.

  =item getipnodebyname HOST, [FAMILY, FLAGS]

      This function takes either a node name or an IP address string
      and performs a lookup on that name (or conversion of the string).
      It returns a list of five elements: the canonical host name,
      the address family, the length in octets of the IP addresses
      returned, a reference to a list of IP address structures, and
      a reference to a list of aliases for the host name.

      The arguments FAMILY and FLAGS are optional.
      Note: This function does not handle IPv6 scope identifiers,
      and should be used with care.
      And, this function was deprecated in RFC3493.
      The getnameinfo function should be used instead.

  =item getipnodebyaddr FAMILY, ADDRESS

      This function takes an IP address family and an IP address structure
      and performs a reverse lookup on that address.
      It returns a list of five elements: the canonical host name,
      the address family, the length in octets of the IP addresses
      returned, a reference to a list of IP address structures, and
      a reference to a list of aliases for the host name.

      Note: This function does not handle IPv6 scope identifiers,
      and should be used with care.
      And, this function was deprecated in RFC3493.
      The getaddrinfo function should be used instead.

  =item gai_strerror ERROR_NUMBER

      This function returns a string corresponding to the error number
      passed in as an argument.

  =item in6addr_any

      This function returns the 16-octet wildcard address.

  =item in6add_loopback

      This function returns the 16-octet loopback address.

  =over

  =back


pkgId: 9e2c15b29e7bdafb9f018378bd36a1aa4bfabf572ab57bb31f245e061a0e86bc
name: local-perl-Sphinx-Search
arch: noarch
version: 0.27.2
epoch: 0
release: 1
summary: Sphinx-Search - Sphinx search engine API Perl client
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jon Schutz <jon@jschutz.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Sphinx-Search-0.27.2-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Sphinx-Search-0.27.2-1.noarch.rpm
checksum_type: sha256
description:
  This is the Perl API client for the Sphinx open-source SQL full-text indexing
  search engine, L<http://www.sphinxsearch.com>.


pkgId: 1cbbc043fdcc2acba723ffedfdcf0ea4183759909a4faf567aee04bb48f7e292
name: local-perl-Spreadsheet-ParseExcel
arch: noarch
version: 0.59
epoch: 0
release: 1
summary: Spreadsheet-ParseExcel - Read information from an Excel file.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: John McNamara (jmcnamara@cpan.org)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Spreadsheet-ParseExcel-0.59-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Spreadsheet-ParseExcel-0.59-1.noarch.rpm
checksum_type: sha256
description:
  The Spreadsheet::ParseExcel module can be used to read information from Excel 95-2003 binary files.

  The module cannot read files in the Excel 2007 Open XML XLSX format. See the L<Spreadsheet::XLSX> module instead.


pkgId: d16225edbbac72ae40afd53fa5c73bea2581c8890419fbb0d9c00ccc9881aeb1
name: local-perl-Spreadsheet-WriteExcel
arch: noarch
version: 2.37
epoch: 0
release: 1
summary: Spreadsheet-WriteExcel - Write to a cross platform Excel binary file
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: John McNamara (jmcnamara@cpan.org)
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Spreadsheet-WriteExcel-2.37-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Spreadsheet-WriteExcel-2.37-1.noarch.rpm
checksum_type: sha256
description:
  The Spreadsheet::WriteExcel Perl module can be used to create a cross-platform Excel binary file. Multiple worksheets can be added to a workbook and formatting can be applied to cells. Text, numbers, formulas, hyperlinks, images and charts can be written to the cells.

  The file produced by this module is compatible with Excel 97, 2000, 2002, 2003 and 2007.

  The module will work on the majority of Windows, UNIX and Mac platforms. Generated files are also compatible with the Linux/UNIX spreadsheet applications Gnumeric and OpenOffice.org.

  This module cannot be used to write to an existing Excel file (See L<MODIFYING AND REWRITING EXCEL FILES>).


pkgId: aac12ca70ba12014353990f608fc20596a0f75bd76aeab3388a67a303a4dd605
name: local-perl-Sub-Install
arch: noarch
version: 0.925
epoch: 0
release: 1
summary: Sub-Install - install subroutines into packages easily
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ricardo Signes <rjbs@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Sub-Install-0.925-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Sub-Install-0.925-1.noarch.rpm
checksum_type: sha256
description:
  This module makes it easy to install subroutines into packages without the
  unslightly mess of C<no strict> or typeglobs lying about where just anyone can
  see them.


pkgId: 3d1ed64de4933aa05be485738a19d470c9fa405261546d045eaec0d7c2d03a92
name: local-perl-Task-Weaken
arch: noarch
version: 1.04
epoch: 0
release: 1
summary: Task-Weaken - Ensure that a platform has weaken support
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Adam Kennedy <adamk@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Task-Weaken-1.04-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Task-Weaken-1.04-1.noarch.rpm
checksum_type: sha256
description:
  One recurring problem in modules that use L<Scalar::Util>'s C<weaken>
  function is that it is not present in the pure-perl variant.

  While this isn't necesarily always a problem in a straight CPAN-based
  Perl environment, some operating system distributions only include the
  pure-Perl versions, don't include the XS version, and so weaken is
  then "missing" from the platform, B<despite> passing a dependency on
  L<Scalar::Util> successfully.

  Most notably this is RedHat Linux at time of writing, but other come
  and go and do the same thing, hence "recurring problem".

  The normal solution is to manually write tests in each distribution
  to ensure that C<weaken> is available.

  This restores the functionality testing to a dependency you do once
  in your F<Makefile.PL>, rather than something you have to write extra
  tests for each time you write a module.

  It should also help make the package auto-generators for the various
  operating systems play more nicely, because it introduces a dependency
  that they B<have> to have a proper weaken in order to work.


pkgId: aefbbba872476cda8028d38b58a59a449750eeac26cc08351121eff6bc0bc245
name: local-perl-Template-Toolkit
arch: x86_64
version: 2.22
epoch: 0
release: 1
summary: Template-Toolkit - comprehensive template processing system
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Wardley <abw@wardley.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Template-Toolkit-2.22-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Template-Toolkit-2.22-1.x86_64.rpm
checksum_type: sha256
description:
  This documentation describes the Template module which is the direct
  Perl interface into the Template Toolkit.  It covers the use of the
  module and gives a brief summary of configuration options and template
  directives.  Please see L<Template::Manual> for the complete reference
  manual which goes into much greater depth about the features and use
  of the Template Toolkit.  The L<Template::Tutorial> is also available
  as an introductory guide to using the Template Toolkit.


pkgId: 7c6cc9f4335270e48e9f4ad6ddef3ebccffd0a69a7fa806434c843cde6af12ae
name: local-perl-Term-UI
arch: noarch
version: 0.26
epoch: 0
release: 162.ep
summary: Term::ReadLine UI made easy
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Term-UI-0.26-162.ep.noarch.rpm
checksum_type: sha256
description:
  Term::UI is a transparent way of eliminating the overhead of having to format
  a question and then validate the reply, informing the user if the answer was not
  proper and re-issuing the question.


pkgId: 065b9541a30e692ef34d6c589fd6076a895bdb68f6f6ab18ad34b2d062047e18
name: local-perl-TermReadKey
arch: x86_64
version: 2.30
epoch: 0
release: 6.ep
summary: A perl module for simple terminal control
url: http://search.cpan.org/dist/TermReadKey/
rpm_license: Copyright only
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-TermReadKey-2.30-6.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-TermReadKey-2.30-6.ep.x86_64.rpm
checksum_type: sha256
description:
  Term::ReadKey is a compiled perl module dedicated to providing simple
  control over terminal driver modes (cbreak, raw, cooked, etc.)
  support for non-blocking reads, if the architecture allows, and some
  generalized handy functions for working with terminals.  One of the
  main goals is to have the functions as portable as possible, so you
  can just plug in "use Term::ReadKey" on any architecture and have a
  good likelyhood of it working.


pkgId: 3a6daaf5d2c16d6eb1b55c2b4c09c6a9c48dba84d61777d53828af82b8c90567
name: local-perl-Test-Base
arch: noarch
version: 0.60
epoch: 0
release: 1
summary: Test-Base - A Data Driven Testing Framework
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ingy döt Net <ingy@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-Base-0.60-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Base-0.60-1.noarch.rpm
checksum_type: sha256
description:
  Testing is usually the ugly part of Perl module authoring. Perl gives
  you a standard way to run tests with Test::Harness, and basic testing
  primitives with Test::More. After that you are pretty much on your own
  to develop a testing framework and philosophy. Test::More encourages
  you to make your own framework by subclassing Test::Builder, but that is
  not trivial.

  Test::Base gives you a way to write your own test framework base
  class that I<is> trivial. In fact it is as simple as two lines:

      package MyTestFramework;
      use Test::Base -Base;

  A module called C<MyTestFramework.pm> containing those two lines, will
  give all the power of Test::More and all the power of Test::Base to
  every test file that uses it. As you build up the capabilities of
  C<MyTestFramework>, your tests will have all of that power as well.

  C<MyTestFramework> becomes a place for you to put all of your reusable
  testing bits. As you write tests, you will see patterns and duplication,
  and you can "upstream" them into C<MyTestFramework>. Of course, you
  don't have to subclass Test::Base at all. You can use it directly in
  many applications, including everywhere you would use Test::More.

  Test::Base concentrates on offering reusable data driven patterns, so
  that you can write tests with a minimum of code. At the heart of all
  testing you have inputs, processes and expected outputs. Test::Base
  provides some clean ways for you to express your input and expected
  output data, so you can spend your time focusing on that rather than
  your code scaffolding.


pkgId: d5910121e284055801ce4e7b4a13a8adf0274941e9a5b70200c624bf84b7c6a7
name: local-perl-Test-Exception
arch: noarch
version: 0.40
epoch: 0
release: 1
summary: Test-Exception - Test exception-based code
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Adrian Howard <adrianh@quietstars.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-Exception-0.40-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Exception-0.40-1.noarch.rpm
checksum_type: sha256
description:
  This module provides a few convenience methods for testing exception based code. It is built with
  L<Test::Builder> and plays happily with L<Test::More> and friends.

  If you are not already familiar with L<Test::More> now would be the time to go take a look.

  You can specify the test plan when you C<use Test::Exception> in the same way as C<use Test::More>.
  See L<Test::More> for details.

  NOTE: Test::Exception only checks for exceptions. It will ignore other methods of stopping
  program execution - including exit(). If you have an exit() in evalled code Test::Exception
  will not catch this with any of its testing functions.

  NOTE: This module uses L<Sub::Uplevel> and relies on overriding
  C<CORE::GLOBAL::caller> to hide your test blocks from the call stack.  If this
  use of global overrides concerns you, the L<Test::Fatal> module offers a more
  minimalist alternative.


pkgId: 3f842fea3f9ab04403aae9c1c1d67c3eeb0804dcfcea78286ff6cb1833778658
name: local-perl-Test-Harness
arch: noarch
version: 3.23
epoch: 0
release: 162.ep
summary: Run Perl standard test scripts with statistics
url: http://www.perl.org/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Languages
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-5.14.1-162.ep.src.rpm
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: local-perl-Test-Harness-3.23-162.ep.noarch.rpm
checksum_type: sha256
description:
  Run Perl standard test scripts with statistics.
  Use TAP::Parser, Test::Harness package was whole rewritten.


pkgId: f536d4315e4e733d354b3066b2bc639f9e627a6808b832fd125c9d25c277abc1
name: local-perl-Test-Memory-Cycle
arch: noarch
version: 1.04
epoch: 0
release: 1
summary: Test-Memory-Cycle - Verifies code hasn't left circular references
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Written by Andy <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-Memory-Cycle-1.04-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Memory-Cycle-1.04-1.noarch.rpm
checksum_type: sha256
description:
  Perl's garbage collection has one big problem: Circular references
  can't get cleaned up.  A circular reference can be as simple as two
  reference that refer to each other:

      my $mom = {
          name => "Marilyn Lester",
      };

      my $me = {
          name => "Andy Lester",
          mother => $mom,
      };
      $mom->{son} = $me;

  C<Test::Memory::Cycle> is built on top of C<Devel::Cycle> to give
  you an easy way to check for these circular references.

      use Test::Memory::Cycle;

      my $object = new MyObject;
      
      memory_cycle_ok( $object );

  You can also use C<memory_cycle_exists()> to make sure that you have a
  cycle where you expect to have one.


pkgId: ac34a1c58a6ffc6db2b89675d894dd67408f7120191388c29cfefdd7cd17cccd
name: local-perl-Test-Most
arch: noarch
version: 0.34
epoch: 0
release: 1
summary: Test-Most - Most commonly needed test functions and features.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Curtis Poe C <ovid@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-Most-0.34-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Most-0.34-1.noarch.rpm
checksum_type: sha256
description:
  L<Test::Most> exists to reduce boilerplate and to make your testing life
  easier.  We provide "one stop shopping" for most commonly used testing
  modules.  In fact, we often require the latest versions so that you get bug
  fixes through L<Test::Most> and don't have to keep upgrading these modules
  separately.

  This module provides you with the most commonly used testing functions, along
  with automatically turning on strict and warning and gives you a bit more
  fine-grained control over your test suite.

      use Test::Most tests => 4, 'die';

      ok 1, 'Normal calls to ok() should succeed';
      is 2, 2, '... as should all passing tests';
      eq_or_diff [3], [4], '... but failing tests should die';
      ok 4, '... will never get to here';

  As you can see, the C<eq_or_diff> test will fail.  Because 'die' is in the
  import list, the test program will halt at that point.

  If you do not want strict and warnings enabled, you must explicitly disable
  them.  Thus, you must be explicit about what you want and no longer need to
  worry about accidentally forgetting them.

      use Test::Most tests => 4;
      no strict;
      no warnings;


pkgId: 53982265c2f9648e20f80650f27f3a1d637a3450d3e622aa15e66a51d048173e
name: local-perl-Test-NoWarnings
arch: noarch
version: 1.02
epoch: 0
release: 1
summary: Test-NoWarnings - Make sure you didn't emit any warnings while testing
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Fergal Daly <fergal@esatclear.ie>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-NoWarnings-1.02-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-NoWarnings-1.02-1.noarch.rpm
checksum_type: sha256
description:
  In general, your tests shouldn't produce warnings. This modules causes any
  warnings to be captured and stored. It automatically adds an extra test that
  will run when your script ends to check that there were no warnings. If
  there were any warings, the test will give a "not ok" and diagnostics of
  where, when and what the warning was, including a stack trace of what was
  going on when the it occurred.

  If some of your tests B<are supposed to> produce warnings then you should be
  capturing and checking them with L<Test::Warn>, that way L<Test::NoWarnings>
  will not see them and so not complain.

  The test is run by an END block in Test::NoWarnings. It will not be run when
  any forked children exit.


pkgId: f029fc910a92b36b14d556ff05d6be19fb555c26745d9b816a5715d9da2ce90a
name: local-perl-Test-NoWarnings
arch: noarch
version: 1.04
epoch: 0
release: 1
summary: Test-NoWarnings - Make sure you didn't emit any warnings while testing
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Fergal Daly <fergal@esatclear.ie>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-NoWarnings-1.04-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-NoWarnings-1.04-1.noarch.rpm
checksum_type: sha256
description:
  In general, your tests shouldn't produce warnings. This modules causes any
  warnings to be captured and stored. It automatically adds an extra test that
  will run when your script ends to check that there were no warnings. If
  there were any warings, the test will give a "not ok" and diagnostics of
  where, when and what the warning was, including a stack trace of what was
  going on when the it occurred.

  If some of your tests B<are supposed to> produce warnings then you should be
  capturing and checking them with L<Test::Warn>, that way L<Test::NoWarnings>
  will not see them and so not complain.

  The test is run by an C<END> block in Test::NoWarnings. It will not be run
  when any forked children exit.


pkgId: da2dd189c0cbd922f8ec1c2a531e5fc070e91dc9c6166d57164dbbc0f19ac872
name: local-perl-Test-Pod
arch: noarch
version: 1.51
epoch: 0
release: 1
summary: Test-Pod - check for POD errors in files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: David E. Wheeler <david@justatheory.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-Pod-1.51-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Pod-1.51-1.noarch.rpm
checksum_type: sha256
description:
  Check POD files for errors or warnings in a test file, using
  C<Pod::Simple> to do the heavy lifting.


pkgId: bfdf39c907d5637e2cba0ac64a01c3e8a0fb19f785474ef2099273baade630da
name: local-perl-Test-Pod-Coverage
arch: noarch
version: 1.08
epoch: 0
release: 1
summary: Test-Pod-Coverage - Check for pod coverage in your distribution
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Lester C <andy@petdance.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-Pod-Coverage-1.08-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Pod-Coverage-1.08-1.noarch.rpm
checksum_type: sha256
description:
  Checks for POD coverage in files for your distribution.

      use Test::Pod::Coverage tests=>1;
      pod_coverage_ok( "Foo::Bar", "Foo::Bar is covered" );

  Can also be called with L<Pod::Coverage> parms.

      use Test::Pod::Coverage tests=>1;
      pod_coverage_ok(
          "Foo::Bar",
          { also_private => [ qr/^[A-Z_]+$/ ], },
          "Foo::Bar, with all-caps functions as privates",
      );

  The L<Pod::Coverage> parms are also useful for subclasses that don't
  re-document the parent class's methods.  Here's an example from
  L<Mail::SRS>.

      pod_coverage_ok( "Mail::SRS" ); # No exceptions

      
      my $trustme = { trustme => [qr/^(new|parse|compile)$/] };
      pod_coverage_ok( "Mail::SRS::DB", $trustme );
      pod_coverage_ok( "Mail::SRS::Guarded", $trustme );
      pod_coverage_ok( "Mail::SRS::Reversable", $trustme );
      pod_coverage_ok( "Mail::SRS::Shortcut", $trustme );

  Alternately, you could use L<Pod::Coverage::CountParents>, which always allows
  a subclass to reimplement its parents' methods without redocumenting them.  For
  example:

      my $trustparents = { coverage_class => 'Pod::Coverage::CountParents' };
      pod_coverage_ok( "IO::Handle::Frayed", $trustparents );

  (The C<coverage_class> parameter is not passed to the coverage class with other
  parameters.)

  If you want POD coverage for your module, but don't want to make
  Test::Pod::Coverage a prerequisite for installing, create the following
  as your F<t/pod-coverage.t> file:

      use Test::More;
      eval "use Test::Pod::Coverage";
      plan skip_all => "Test::Pod::Coverage required for testing pod coverage" if $@;

      plan tests => 1;
      pod_coverage_ok( "Pod::Master::Html");

  Finally, Module authors can include the following in a F<t/pod-coverage.t>
  file and have C<Test::Pod::Coverage> automatically find and check all
  modules in the module distribution:

      use Test::More;
      eval "use Test::Pod::Coverage 1.00";
      plan skip_all => "Test::Pod::Coverage 1.00 required for testing POD coverage" if $@;
      all_pod_coverage_ok();


pkgId: 06c8b07496488aebd4f229dc3199b0037b42eca4c721789c423115b61d285b8c
name: local-perl-Test-Requires
arch: noarch
version: 0.06
epoch: 0
release: 1
summary: Test-Requires - Checks to see if the module can be loaded
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tokuhiro Matsuno <tokuhirom @*(#RJKLFHFSDLJF gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-Requires-0.06-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Requires-0.06-1.noarch.rpm
checksum_type: sha256
description:
  Test::Requires checks to see if the module can be loaded.

  If this fails rather than failing tests this B<skips all tests>.


pkgId: 255b5485d498bf28e5891583094a3fc9309d8670d1b6709d706a2642dda551e0
name: local-perl-Test-SharedFork
arch: noarch
version: 0.19
epoch: 0
release: 1
summary: Test-SharedFork - fork test
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tokuhiro Matsuno <tokuhirom slkjfd gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-SharedFork-0.19-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-SharedFork-0.19-1.noarch.rpm
checksum_type: sha256
description:
  Test::SharedFork is utility module for Test::Builder.

  This module makes L<fork(2)> safety in your test case.

  This module merges test count with parent process & child process.


pkgId: 815c1fcb9a90f425b5d51433de416818ba96e964017dcd9805916e493817cb1f
name: local-perl-Test-Simple
arch: noarch
version: 1.302012_002
epoch: 0
release: 1
summary: Test-Simple - Basic utilities for writing tests.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Michael G Schwern <schwern@pobox.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-Simple-1.302012_002-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Simple-1.302012_002-1.noarch.rpm
checksum_type: sha256
description:
  ** If you are unfamiliar with testing B<read L<Test::Tutorial> first!> **

  This is an extremely simple, extremely basic module for writing tests
  suitable for CPAN modules and other pursuits.  If you wish to do more
  complicated testing, use the Test::More module (a drop-in replacement
  for this one).

  The basic unit of Perl testing is the ok.  For each thing you want to
  test your program will print out an "ok" or "not ok" to indicate pass
  or fail.  You do this with the C<ok()> function (see below).

  The only other constraint is you must pre-declare how many tests you
  plan to run.  This is in case something goes horribly wrong during the
  test and your test program aborts, or skips a test or whatever.  You
  do this like so:

      use Test::Simple tests => 23;

  You must have a plan.


  =over 4

  =item B<ok>

    ok( $foo eq $bar, $name );
    ok( $foo eq $bar );

  C<ok()> is given an expression (in this case C<$foo eq $bar>).  If it's
  true, the test passed.  If it's false, it didn't.  That's about it.

  C<ok()> prints out either "ok" or "not ok" along with a test number (it
  keeps track of that for you).

    
    ok( get_temperature($hell) > 0, 'Hell not yet frozen over' );

  If you provide a $name, that will be printed along with the "ok/not
  ok" to make it easier to find your test when if fails (just search for
  the name).  It also makes it easier for the next guy to understand
  what your test is for.  It's highly recommended you use test names.

  All tests are run in scalar context.  So this:

      ok( @stuff, 'I have some stuff' );

  will do what you mean (fail if stuff is empty)


pkgId: f5db62d6512633d41f8f9796041fc43bb13233db44ca21590d696a8ed5929a43
name: local-perl-Test-Taint
arch: x86_64
version: 1.04
epoch: 0
release: 1
summary: Test-Taint - Checks for taintedness of variables
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Lester C <andy@petdance.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-Taint-1.04-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Taint-1.04-1.x86_64.rpm
checksum_type: sha256
description:
  Tainted data is data that comes from an unsafe source, such as the
  command line, or, in the case of web apps, any GET or POST transactions.
  Read the L<perlsec> man page for details on why tainted data is bad,
  and how to untaint the data.

  When you're writing unit tests for code that deals with tainted data,
  you'll want to have a way to provide tainted data for your routines to
  handle, and easy ways to check and report on the taintedness of your data,
  in standard L<Test::More> style.


pkgId: d9e4833aee791460cf4b1e69711f3eb0363ff05ec24c3404d2ed685ca48846d7
name: local-perl-Test-Tester
arch: noarch
version: 0.107
epoch: 0
release: 1
summary: Test-Tester - Ease testing test modules built with Test::Builder
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Fergal Daly <fergal@esatclear.ie>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-Tester-0.107-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Tester-0.107-1.noarch.rpm
checksum_type: sha256
description:
  If you have written a test module based on Test::Builder then Test::Tester
  allows you to test it with the minimum of effort.


pkgId: a96fa6aec7b16bec97f756218bc396ec1b377ef8438bc139736c664723cc4374
name: local-perl-Test-Warn
arch: noarch
version: 0.23
epoch: 0
release: 1
summary: Test-Warn - Perl extension to test methods for warnings
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Alexandr Ciornii <alexchorny@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Test-Warn-0.23-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Warn-0.23-1.noarch.rpm
checksum_type: sha256
description:
  A good style of Perl programming calls for a lot of diverse regression tests.

  This module provides a few convenience methods for testing warning based code.

  If you are not already familiar with the Test::More manpage
  now would be the time to go take a look.


pkgId: 2dc3a5c15618a483f4aa8e47ada92b01ab7040c211b43e7668f78d229f725451
name: local-perl-Text-Diff
arch: noarch
version: 1.43
epoch: 0
release: 1
summary: Text-Diff - Perform diffs on files and record sets
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Adam Kennedy <adamk@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Text-Diff-1.43-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-Diff-1.43-1.noarch.rpm
checksum_type: sha256
description:
  C<diff()> provides a basic set of services akin to the GNU C<diff> utility.  It
  is not anywhere near as feature complete as GNU C<diff>, but it is better
  integrated with Perl and available on all platforms.  It is often faster than
  shelling out to a system's C<diff> executable for small files, and generally
  slower on larger files.

  Relies on L<Algorithm::Diff> for, well, the algorithm.  This may not produce
  the same exact diff as a system's local C<diff> executable, but it will be a
  valid diff and comprehensible by C<patch>.  We haven't seen any differences
  between Algorithm::Diff's logic and GNU diff's, but we have not examined them
  to make sure they are indeed identical.

  B<Note>: If you don't want to import the C<diff> function, do one of the
  following:

     use Text::Diff ();

     require Text::Diff;

  That's a pretty rare occurence, so C<diff()> is exported by default.

  If you pass a filename, but the file can't be read,
  then C<diff()> will C<croak>.


pkgId: 76ecf8fa0a17be8bb21c23fac4b8ce300ed5e53a1303c4904a6bd6258be8e142
name: local-perl-Text-Query
arch: noarch
version: 0.07
epoch: 0
release: 1
summary: Text-Query - Query processing framework
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Eric Bohlman <ebohlman@netcom.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Text-Query-0.07-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-Query-0.07-1.noarch.rpm
checksum_type: sha256
description:
  This module provides an object that matches a data source
  against a query expression.

  Query expressions are compiled into an internal form when a new object is created
  or the C<prepare> method is
  called; they are not recompiled on each match.

  The class provided by this module uses four packages to process the query.
  The query parser parses the question and calls a query expression
  builder (internal form of the question). The optimizer is then called
  to reduce the complexity of the expression. The solver applies the expression
  on a data source.

  The following parsers are provided:

  =over 4

  =item Text::Query::ParseAdvanced

  =item Text::Query::ParseSimple

  =back

  The following builders are provided:

  =over 4

  =item Text::Query::BuildAdvancedString

  =item Text::Query::BuildSimpleString

  =back

  The following solver is provided:

  =over 4

  =item Text::Query::SolveSimpleString

  =item Text::Query::SolveAdvancedString

  =back


pkgId: d687b25cea6cbc1ee883f17499b1275081cd0df23789773004a3c1538aab9b94
name: local-perl-Tie-ShadowHash
arch: noarch
version: 1.00
epoch: 0
release: 1
summary: Tie-ShadowHash - Merge multiple data sources into a hash
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Russ Allbery <rra@stanford.edu>
rpm_group: Applications/CPAN
rpm_buildhost: rhel6-build64.endpoint.com
rpm_sourcerpm: local-perl-Tie-ShadowHash-1.00-1.src.rpm
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Tie-ShadowHash-1.00-1.noarch.rpm
checksum_type: sha256
description:
  This module merges together multiple sets of data in the form of hashes
  into a data structure that looks to Perl like a single simple hash.  When
  that hash is accessed, the data structures managed by that shadow hash are
  searched in order they were added for that key.  This allows the rest of a
  program simple and convenient access to a disparate set of data sources.

  Tie::ShadowHash can handle anything that looks like a hash; just give it a
  reference as one of the additional arguments to tie().  This includes
  other tied hashes, so you can include DB and DBM files as data sources for
  a shadow hash.  If given a plain file name instead of a reference, it will
  build a hash to use internally, with each chomped line of the file being
  the key and the number of times that line is seen in the file being the
  value.

  Tie::Shadowhash also supports special tagged data sources that can take
  options specifying their behavior.  The only tagged data source currently
  supported is C<text>, which takes a file name of a text file and a
  reference to a sub.  The sub is called for every line of the file, with
  that line as an argument, and is expected to return a list.  The first
  element of the list will be the key, and the second and subsequent
  elements will be the value or values.  If there is more than one value,
  the value stored in the hash and associated with that key is an anonymous
  array containing all of them.

  Tagged data sources are distinguished from normal data sources by passing
  them to tie() (or to add() -- see below) as an anonymous array.  The first
  element is the data source tag and the remaining elements are arguments
  for that data source.  For a text data source, see the usage summary above
  for examples.

  The shadow hash can be modified, and the modifications override the data
  sources, but modifications aren't propagated back to the data sources.  In
  other words, the shadow hash treats all data sources as read-only and
  saves your modifications only in internal memory.  This lets you make
  changes to the shadow hash for the rest of your program without affecting
  the underlying data in any way (and this behavior is the main reason why
  this is called a shadow hash).

  If the shadow hash is cleared, by assigning the empty list to it, by
  explicitly calling CLEAR(), or by some other method, all data sources are
  dropped from the shadow hash.  There is no other way of removing a data
  source from a shadow hash after it's been added (you can, of course,
  always untie the shadow hash and dispose of the underlying object if you
  saved it to destroy the shadow hash completely).


