# packages

pkgId: 8afa124a9ff08dad0bd545766d8361ddbb47b2b4
name: local-perl-Log-Dispatch-FileRotate
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Log-Dispatch-FileRotate-1.19-1.src.rpm
checksum_type: sha
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: c847aab58c4265d1ca559160607f4f1e75ab7955
name: local-perl-Log-Log4perl
arch: src
version: 1.21
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Log-Log4perl-1.21-1.src.rpm
checksum_type: sha
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: 13064de66d4f26929c549c5172c4627167b29b5e
name: local-perl-MIME-Base64-URLSafe
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MIME-Base64-URLSafe-0.01-1.src.rpm
checksum_type: sha
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: daf5fb6247c93c517c6036a854cc1167a90daaae
name: local-perl-MIME-Lite
arch: src
version: 3.021
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MIME-Lite-3.021-1.src.rpm
checksum_type: sha
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: 328dec3b84bce1a6eb00c125bbd9a1e83d22b9b0
name: local-perl-MIME-tools
arch: src
version: 5.427
epoch: 0
release: 1
summary: MIME-tools - Tools to manipulate MIME messages
description: None.
url: http://www.cpan.org
rpm_license: Artistic
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MIME-tools-5.427-1.src.rpm
checksum_type: sha
rpm_vendor:
  Eryq <eryq@zeegee.com>, David F. Skoll <dfs@roaringpenguin.com>, Dave O'Neill <dmo@roaringpenguin.com>


pkgId: 66f7143f8154cae658a4d4e90d47236574371b22
name: local-perl-MRO-Compat
arch: src
version: 0.12
epoch: 0
release: 1
summary: MRO-Compat - mro::* interface compatibility for Perls < 5.9.5
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Brandon L. Black, <blblack@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MRO-Compat-0.12-1.src.rpm
checksum_type: sha
description:
  The "mro" namespace provides several utilities for dealing
  with method resolution order and method caching in general
  in Perl 5.9.5 and higher.

  This module provides those interfaces for
  earlier versions of Perl (back to 5.6.0 anyways).

  It is a harmless no-op to use this module on 5.9.5+.  That
  is to say, code which properly uses L<MRO::Compat> will work
  unmodified on both older Perls and 5.9.5+.

  If you're writing a piece of software that would like to use
  the parts of 5.9.5+'s mro:: interfaces that are supported
  here, and you want compatibility with older Perls, this
  is the module for you.

  Some parts of this code will work better and/or faster with
  L<Class::C3::XS> installed (which is an optional prereq
  of L<Class::C3>, which is in turn a prereq of this
  package), but it's not a requirement.

  This module never exports any functions.  All calls must
  be fully qualified with the C<mro::> prefix.

  The interface documentation here serves only as a quick
  reference of what the function basically does, and what
  differences between L<MRO::Compat> and 5.9.5+ one should
  look out for.  The main docs in 5.9.5's L<mro> are the real
  interface docs, and contain a lot of other useful information.


pkgId: 847c11f7c392e7cfa724ee363bc0cd66d351cd3b
name: local-perl-Mail-Box
arch: src
version: 2.082
epoch: 0
release: 1
summary: Manage a mailbox, a folder with messages
url: http://search.cpan.org/dist/Mail-Box/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation
rpm_group: Development/Libraries
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: local-perl-Mail-Box-2.082-1.src.rpm
checksum_type: sha
description:
  The Mail::Box folder is a modern mail-folder manager -- at least at
  the moment of this writing ;)  It is written to replace Mail::Folder,
  although its interface is different.


pkgId: a1b1649e88cffd33466b3f337d015816475e94de
name: local-perl-Mail-Box-Parser-C
arch: src
version: 3.006
epoch: 0
release: 1
summary: Mail-Box-Parser-C - C parser for Mail::Box
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Mark Overmeer
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-Box-Parser-C-3.006-1.src.rpm
checksum_type: sha
description:
  This is an optional module for MailBox, and will (once installed)
  automatically be used by MailBox to parse e-mail message content when
  the message is supplied as file-handle.  In all other cases,
  MailBox will use L<Mail::Box::Parser::Perl>.


pkgId: 891d42facf518c3cfb2c7beb77fb1fd06bf3c8e4
name: local-perl-Mail-Bulkmail
arch: src
version: 3.12
epoch: 0
release: 1
summary: Mail-Bulkmail - used to create subclasses for Mail::Bulkmail.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jim Thomason <jim@jimandkoka.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-Bulkmail-3.12-1.src.rpm
checksum_type: sha
description:
  Older versions of this code used to be contained within the Mail::Bulkmail package itself, but since 3.00 now has
  all of the code compartmentalized, I couldn't leave this in there. Well, technically I *could*, but I didn't like that.
  It's wasteful to make Mail::Bulkmail::Server a subclass of Mail::Bulkmail, for instance, since they don't share
  any methods, attributes, whatever. Well, none beyond the standard object methods that I like to use. Hence this module
  was born.

  Of course, you don't have to use this to create subclasses, but you'll run the risk of making something with an inconsistent
  interface vs. the rest of the system. That'll confuse people and make them unhappy. So I recommend subclassing off of here
  to be consistent. Of course, you may not like these objects, but they do work well and are consistent. Consistency is
  very important in interface design, IMHO.


pkgId: 190f42a8c50056d1c67f047ad78e0345518d0cb8
name: local-perl-Mail-POP3Client
arch: src
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-POP3Client-2.18-1.src.rpm
checksum_type: sha
description:
  This module implements an Object-Oriented interface to a POP3 server.
  It implements RFC1939 (http://www.faqs.org/rfcs/rfc1939.html)


pkgId: bbe75c25e0566fb14e52d758752afd6fe745285b
name: local-perl-Mail-RFC822-Address
arch: src
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: rhel5-build32
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-RFC822-Address-0.3-1.src.rpm
checksum_type: sha
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: b61c7aeb645dc0955e700f617aa58a82a6973d72
name: local-perl-Mail-Sender
arch: src
version: 0.8.16
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-Sender-0.8.16-1.src.rpm
checksum_type: sha
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: 43aec21b99d475095275ab15f70fea3b657eb2fe
name: local-perl-Mail-Sendmail
arch: src
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-Sendmail-0.79_16-1.src.rpm
checksum_type: sha
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: 6c7ed31da6a442103fadf0ee7b8652075f144354
name: local-perl-Mail-SpamAssassin
arch: src
version: 3.002005
epoch: 0
release: 1
summary: Mail-SpamAssassin - SpamAssassin is an extensible email filter which is used to identify spam.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: The Apache SpamAssassin Project <dev@spamassassin.apache.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-SpamAssassin-3.002005-1.src.rpm
checksum_type: sha
description:
  Mail::SpamAssassin is a module to identify spam using several methods
  including text analysis, internet-based realtime blacklists, statistical
  analysis, and internet-based hashing algorithms.

  Using its rule base, it uses a wide range of heuristic tests on mail
  headers and body text to identify "spam", also known as unsolicited bulk
  email.  Once identified as spam, the mail can then be tagged as spam for
  later filtering using the user's own mail user agent application or at
  the mail transfer agent.

  If you wish to use a command-line filter tool, try the C<spamassassin>
  or the C<spamd>/C<spamc> tools provided.


pkgId: 395ea62e3bb52a413e6f34b141a87715ef598d5a
name: local-perl-Mail-Transport-Dbx
arch: src
version: 0.07
epoch: 0
release: 1
summary: Mail-Transport-Dbx - Parse Outlook Express mailboxes
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tassilo von Parseval <tassilo.parseval@rwth-aachen.de>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-Transport-Dbx-0.07-1.src.rpm
checksum_type: sha
description:
  Mail::Transport::Dbx gives you platform independent access to Outlook Express' dbx files.  Extract subfolders, messages etc. from those or use it to convert dbx archives into a more portable format (such as standard mbox format).

  It relies on LibDBX to do its job. The bad news: LibDBX knows nothing about the endianness of your machine so it does not work on big-endian machines such as Macintoshs or SUNs. The good news: I made the appropriate patches so that it in fact does work even on machines with the 'wrong' byteorder (exception: machines with an even odder byteorder such as Crays are not suppored; exception from the exception: If you buy me a Cray I'll promise to fix it. :-).

  You have to understand the structure of .dbx files to make proper use of this module. Outlook Express keeps a couple of those files on your harddisk. For instance:

      Folders.dbx
      folder1.dbx
      comp.lang.perl.misc.dbx

  The nasty thing about that is that there are really two different kinds of such files: One that contains the actual messages and one that merely holds references to other .dbx files. F<Folders.dbx> could be considered the toplevel file since it lists all other available .dbx files. As for folder1.dbx and comp.lang.perl.misc.dbx you can't yet know whether they contain messages or subfolders (though comp.lang.perl.misc.dbx probably contains newsgroup messages that are treated as mere emails).

  Fortunately this module gives you the information you need. A common approach would be the following:

      1) create a new Mail::Transport::Dbx object from "Folders.dbx"

      2) iterate over its items using the get() method
          2.1 if it returns a Mail::Transport::Dbx::Email
              => a message
          2.2 if it returns a Mail::Transport::Dbx::Folder
              => a folder

      3) if message
          3.1 call whatever method from Mail::Transport::Dbx::Email
              you need

      4) if folder
          4.1 call whatever method from Mail::Transport::Dbx::Folder
              you need
          OR
          4.2 call dbx() on it to create a new Mail::Transport::Dbx
              object
              4.2.1 if dbx() returned something defined
                    => rollback to item 2)

  The confusing thing is that .dbx files may contain references to other folders that don't really exist! If Outlook Express was used a newsclient this is a common scenario since Folders.dbx lists B<all> newsgroups as separate C<Mail::Transport::Dbx::Folder> objects no matter whether you are subscribed to any of those or not. So in essence calling C<dbx()> on a folder will only return a new object if the corresponding .dbx file exists.


pkgId: 785af8454be49fc972e944216949ab10b44f86f3
name: local-perl-Mail-VRFY
arch: src
version: 0.58
epoch: 0
release: 1
summary: Mail-VRFY - Utility to verify an email address
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jeremy Kister <http://jeremy.kister.net/>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mail-VRFY-0.58-1.src.rpm
checksum_type: sha
description:
  C<Mail::VRFY> was derived from Pete Fritchman's L<Mail::Verify>.
  Lots of code has been plucked.  This package attempts to be
  completely compatibile with Mail::Verify.

  C<Mail::VRFY> provides a C<CheckAddress> function for verifying email
  addresses.  Lots can be checked, according to the C<method> option,
  as described below.

  C<Mail::VRFY> differs from L<Mail::Verify> in that:

  A.  More granular control over what kind of checks to run
      (via the method option).

  B.  Email address syntax checking is much more stringent.

  C.  After making a socket to an authoritative SMTP server,
      we can start a SMTP converstation, to ensure the
      mailserver does not give a failure on RCPT TO.

  D.  More return codes.


pkgId: 919999df5bf91f2af0c3a1c834750f4db55f43f6
name: local-perl-Math-BigInt-GMP
arch: src
version: 1.24
epoch: 0
release: 1
summary: Math-BigInt-GMP - Use the GMP library for Math::BigInt routines
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tels httpbloodgatecom in <>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Math-BigInt-GMP-1.24-1.src.rpm
checksum_type: sha
description:
  Provides support for big integer calculations via means of the GMP c-library.

  Math::BigInt::GMP now no longer uses Math::GMP, but provides it's own XS layer
  to access the GMP c-library. This cut's out another (perl sub routine) layer
  and also reduces the memory footprint by not loading Math::GMP and Carp at
  all.


pkgId: 1332b0c5ba2a5ae97da8723112ab489b011b776c
name: local-perl-Math-GMP
arch: src
version: 2.04
epoch: 0
release: 1
summary: Math-GMP - High speed arbitrary size integer math
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Chip Turner <chip@redhat.com,>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Math-GMP-2.04-1.src.rpm
checksum_type: sha
description:
  Math::GMP was designed to be a drop-in replacement both for
  Math::BigInt and for regular integer arithmetic.  Unlike BigInt,
  though, Math::GMP uses the GNU gmp library for all of its
  calculations, as opposed to straight Perl functions.  This can result
  in speed improvements.

  The downside is that this module requires a C compiler to install -- a
  small tradeoff in most cases. Also, this module is not 100% compatible
  to Math::BigInt.

  A Math::GMP object can be used just as a normal numeric scalar would
  be -- the module overloads most of the normal arithmetic operators to
  provide as seamless an interface as possible. However, if you need a
  perfect interface, you can do the following:

    use Math::GMP qw(:constant);

    $n = 2 ** (256 * 1024);
    print "n is $n\n";

  This would fail without the ':constant' since Perl would use normal
  doubles to compute the 250,000 bit number, and thereby overflow it
  into meaninglessness (smaller exponents yield less accurate data due
  to floating point rounding).


pkgId: 22833267af6d2e73df7c176ca6c25d8728273a19
name: local-perl-Math-Pari
arch: src
version: 2.010709
epoch: 0
release: 7
summary: Perl interface to PARI
url: http://search.cpan.org/dist/Math-Pari/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation
rpm_group: Development/Libraries
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: local-perl-Math-Pari-2.010709-7.src.rpm
checksum_type: sha
description:
  This package is a Perl interface to the famous library PARI for numerical/
  scientific/ number-theoretic calculations. It allows use of most PARI functions
  as Perl functions, and (almost) seamless merging of PARI and Perl data.


pkgId: ae95591c71e9e798945e3b91dce269985f7773f2
name: local-perl-Math-Pari
arch: src
version: 2.010800
epoch: 0
release: 1
summary: Math-Pari - Perl interface to PARI.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ilya Zakharevich <Iilyaz@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Math-Pari-2.010800-1.src.rpm
checksum_type: sha
description:
  This package is a Perl interface to famous library PARI for
  numerical/scientific/number-theoretic calculations.  It allows use of
  most PARI functions as Perl functions, and (almost) seamless merging
  of PARI and Perl data. In what follows we suppose prior knowledge of
  what PARI is (see L<ftp://megrez.math.u-bordeaux.fr/pub/pari>, or
  L<Math::libPARI>).


pkgId: fd5dfcce2965bf8512c6412ebe406ce7b8c1f257
name: local-perl-Math-Random-MT-Auto
arch: src
version: 6.14
epoch: 0
release: 1
summary: Math-Random-MT-Auto - Auto-seeded Mersenne Twister PRNGs
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jerry D. Hedden <jdhedden AT cpan DOT org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Math-Random-MT-Auto-6.14-1.src.rpm
checksum_type: sha
description:
  The Mersenne Twister is a fast pseudorandom number generator (PRNG) that is
  capable of providing large volumes (> 10^6004) of "high quality" pseudorandom
  data to applications that may exhaust available "truly" random data sources or
  system-provided PRNGs such as L<rand|perlfunc/"rand">.

  This module provides PRNGs that are based on the Mersenne Twister.  There
  is a functional interface to a single, standalone PRNG, and an OO interface
  (based on the inside-out object model as implemented by the
  L<Object::InsideOut> module) for generating multiple PRNG objects.  The PRNGs
  are normally self-seeding, automatically acquiring a (19968-bit) random seed
  from user-selectable sources.  (I<Manual> seeding is optionally available.)

  =over

  =item Random Number Deviates

  In addition to integer and floating-point uniformly-distributed random number
  deviates (i.e., L<"irand"> and L<"rand">), this module implements the
  following non-uniform deviates as found in I<Numerical Recipes in C>:

  =over

  =over

  =item * Gaussian (normal)

  =item * Exponential

  =item * Erlang (gamma of integer order)

  =item * Poisson

  =item * Binomial

  =back

  =back

  =item Shuffling

  This module also provides a subroutine/method for shuffling data based on the
  Fisher-Yates shuffling algorithm.

  =item Support for 64-bit Integers

  If Perl has been compiled to support 64-bit integers (do
  L<perl -V|perlrun/"-V"> and look for C<use64bitint=define>), then this module
  will use a 64-bit-integer version of the Mersenne Twister, thus providing
  64-bit random integers and 52-bit random doubles.  The size of integers
  returned by L</"irand">, and used by L</"get_seed"> and L</"set_seed"> will be
  sized accordingly.

  Programmatically, the size of Perl's integers can be determined using the
  C<Config> module:

   use Config;
   print("Integers are $Config{'uvsize'} bytes in length\n");

  =back

  The code for this module has been optimized for speed.  Under Cygwin, it's
  2.5 times faster than Math::Random::MT, and under Solaris, it's more than
  four times faster.  (Math::Random::MT fails to build under Windows.)


pkgId: 2d4062a39b90d9c88197d6e20015a0fb89bffdbc
name: local-perl-Math-Round
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Math-Round-0.06-1.src.rpm
checksum_type: sha
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: d3bf7343d585038446dabb6576c0dc858f58cbde
name: local-perl-Mcrypt
arch: src
version: 2.5.7.0
epoch: 0
release: 1
summary: Mcrypt - Perl extension for the Mcrypt cryptography library
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Theo Schlossnagle <jesus@omniti.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mcrypt-2.5.7.0-1.src.rpm
checksum_type: sha
description:
  This module wraps the libmcrypt encryption library for easy and convenient
  use from within perl.  Encryption and decryption using a variety of algorithms
  is as easy as a few simple lines of perl.


pkgId: e46feed5b655e3704198345b23f9fe359450c12a
name: local-perl-Module-CoreList
arch: src
version: 2.57
epoch: 0
release: 1
summary: Module-CoreList - what modules shipped with versions of perl
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Richard Clamp <Eltrichardc@unixbeard.netEgt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Module-CoreList-2.57-1.src.rpm
checksum_type: sha
description:
  Module::CoreList provides information on which core and dual-life modules shipped
  with each version of L<perl>.

  It provides a number of mechanisms for querying this information.

  There is a utility called L<corelist> provided with this module
  which is a convenient way of querying from the command-line.

  There is a functional programming API available for programmers to query
  information.

  Programmers may also query the contained hash structures to find relevant
  information.


pkgId: f4f5f365d840477981f64e9872b4ae6127b52409
name: local-perl-Module-Find
arch: src
version: 0.06
epoch: 0
release: 1
summary: Module-Find - Find and use installed modules in a (sub)category
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Christian Renz <crenz@web42.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Module-Find-0.06-1.src.rpm
checksum_type: sha
description:
  Module::Find lets you find and use modules in categories. This can be very
  useful for auto-detecting driver or plugin modules. You can differentiate
  between looking in the category itself or in all subcategories.

  If you want Module::Find to search in a certain directory on your
  harddisk (such as the plugins directory of your software installation),
  make sure you modify C<@INC> before you call the Module::Find functions.


pkgId: c6565824aa0c08ecb0804da8ba825369798b2e7c
name: local-perl-Module-Load
arch: src
version: 0.22
epoch: 0
release: 1
summary: Module-Load - Load modules in a DWIM style
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jos Boumans <kane[at]cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Module-Load-0.22-1.src.rpm
checksum_type: sha
description:
  C<load> eliminates the need to know whether you are trying to require
  either a file or a module.

  If you consult C<perldoc -f require> you will see that C<require> will
  behave differently when given a bareword or a string.

  In the case of a string, C<require> assumes you are wanting to load a
  file. But in the case of a bareword, it assumes you mean a module.

  This gives nasty overhead when you are trying to dynamically require
  modules at runtime, since you will need to change the module notation
  (C<Acme::Comment>) to a file notation fitting the particular platform
  you are on.

  C<load> eliminates the need for this overhead and will just DWYM.


pkgId: cc84f6fafbaca5fb5966c33a1abafb30f775a3a2
name: local-perl-Module-Load-Conditional
arch: src
version: 0.46
epoch: 0
release: 1
summary: Module-Load-Conditional - Looking up module information / loading at runtime
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jos Boumans <kane[at]cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Module-Load-Conditional-0.46-1.src.rpm
checksum_type: sha
description:
  Module::Load::Conditional provides simple ways to query and possibly load any of
  the modules you have installed on your system during runtime.

  It is able to load multiple modules at once or none at all if one of
  them was not able to load. It also takes care of any error checking
  and so forth.


pkgId: 788cbbc5926e2e104d037c1fcd134daee4fa9cd9
name: local-perl-Module-Loaded
arch: src
version: 0.08
epoch: 0
release: 1
summary: Module-Loaded - Mark modules as loaded/unloaded
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jos Boumans <kane[at]cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Module-Loaded-0.08-1.src.rpm
checksum_type: sha
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 C<%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: eebe6126252e039487d77120fee3dd76a6067a6d
name: local-perl-Module-Metadata
arch: src
version: 1.000004
epoch: 0
release: 1
summary: Module-Metadata - Gather package and POD information from perl module files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ken Williams <kwilliams@cpan.org,>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Module-Metadata-1.000004-1.src.rpm
checksum_type: sha
description:
  =over 4

  =item new_from_file($filename, collect_pod => 1)

  Construct a C<ModuleInfo> object given the path to a file. Takes an optional
  argument C<collect_pod> which is a boolean that determines whether
  POD data is collected and stored for reference. POD data is not
  collected by default. POD headings are always collected.

  =item new_from_module($module, collect_pod => 1, inc => \@dirs)

  Construct a C<ModuleInfo> object given a module or package name. In addition
  to accepting the C<collect_pod> argument as described above, this
  method accepts a C<inc> argument which is a reference to an array of
  of directories to search for the module. If none are given, the
  default is @INC.

  =item name()

  Returns the name of the package represented by this module. If there
  are more than one packages, it makes a best guess based on the
  filename. If it's a script (i.e. not a *.pm) the package name is
  'main'.

  =item version($package)

  Returns the version as defined by the $VERSION variable for the
  package as returned by the C<name> method if no arguments are
  given. If given the name of a package it will attempt to return the
  version of that package if it is specified in the file.

  =item filename()

  Returns the absolute path to the file.

  =item packages_inside()

  Returns a list of packages.

  =item pod_inside()

  Returns a list of POD sections.

  =item contains_pod()

  Returns true if there is any POD in the file.

  =item pod($section)

  Returns the POD data in the given section.

  =item find_module_by_name($module, \@dirs)

  Returns the path to a module given the module or package name. A list
  of directories can be passed in as an optional parameter, otherwise
  @INC is searched.

  Can be called as either an object or a class method.

  =item find_module_dir_by_name($module, \@dirs)

  Returns the entry in C<@dirs> (or C<@INC> by default) that contains
  the module C<$module>. A list of directories can be passed in as an
  optional parameter, otherwise @INC is searched.

  Can be called as either an object or a class method.

  =item package_versions_from_directory($dir, \@files?)

  Scans C<$dir> for .pm files (unless C<@files> is given, in which case looks
  for those files in C<$dir> - and reads each file for packages and versions,
  returning a hashref of the form:

    {
      'Package::Name' => {
        version => '0.123',
        file => 'Package/Name.pm'
      },
      'OtherPackage::Name' => ...
    }

  =item log_info (internal)

  Used internally to perform logging; imported from Log::Contextual if
  Log::Contextual has already been loaded, otherwise simply calls warn.

  =back


pkgId: 902512ad413ce32ec927946e0fb59c71dcd56e8b
name: local-perl-Module-Metadata
arch: src
version: 1.000007
epoch: 0
release: 1
summary: Module-Metadata - Gather package and POD information from perl module files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: by Ken Williams <kwilliams@cpan.org,>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Module-Metadata-1.000007-1.src.rpm
checksum_type: sha
description:
  This module provides a standard way to gather metadata about a .pm file
  without executing unsafe code.


pkgId: 55c39d7c15e6ceef4126bb0a83f1a3bbe56a9656
name: local-perl-Module-Refresh
arch: src
version: 0.17
epoch: 0
release: 1
summary: Module-Refresh - Refresh %INC files when updated on disk
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jesse Vincent <jesse@bestpractical.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Module-Refresh-0.17-1.src.rpm
checksum_type: sha
description:
  This module is a generalization of the functionality provided by
  L<Apache::StatINC> and L<Apache::Reload>.  It's designed to make it
  easy to do simple iterative development when working in a persistent
  environment.

  It does not require mod_perl.


pkgId: 9c5785bfea0b5317fba019ff8067c42fbff9785c
name: local-perl-Module-Reload
arch: src
version: 1.07
epoch: 0
release: 1
summary: Module-Reload - Reload %INC files when updated on disk
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: jprit@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Module-Reload-1.07-1.src.rpm
checksum_type: sha
description:
  When Perl pulls a file via C<require>, it stores the filename in the
  global hash C<%INC>.  The next time Perl tries to C<require> the same
  file, it sees the file in C<%INC> and does not reload from disk.  This
  module's handler iterates over C<%INC> and reloads the file if it has
  changed on disk.

  Set $Module::Reload::Debug to enable debugging output.


pkgId: 850b0c487a6a3599364d2666b6864b25438a810b
name: local-perl-Module-Reload-Sel
arch: src
version: 1.02
epoch: 0
release: 1
summary: Module-Reload-Sel - Reload perl modules during development
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Chris Thorman <chthorman@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Module-Reload-Sel-1.02-1.src.rpm
checksum_type: sha
description:
  Instead of:

  	use                        Foobar::MyModule;

  Do this:

  	use Module::Reload::Selective;
  	&Module::Reload::Selective->reload(qw(Foobar::MyModule));

  Or, if you need the "import" semantics of "use", do this:

  	use                        Foobar::MyModule    (@ImportArgs);

  Do this:

  	use Module::Reload::Selective;
   	Module::Reload::Selective->reload(qw(Foobar::MyModule));
  	import                     Foobar::MyModule    (@ImportArgs);


  ... then configure your server or other runtime environment settings
  to trigger Module::Reload::Selective to only kick in when you need.

  For example: you could have it kick in only when the web server is
  running on a particular port number or particular (development) host.


pkgId: 18c7991c9d4f9cc8c050f3ae5c8d46bb688cb7e0
name: local-perl-Module-Versions-Report
arch: src
version: 1.06
epoch: 0
release: 1
summary: Module-Versions-Report - report versions of all modules in memory
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sean M Burke <Eltsburke@cpan.orgEgt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Module-Versions-Report-1.06-1.src.rpm
checksum_type: sha
description:
  I often get email from someone reporting a bug in a module I've
  written.  I email back, asking what version of the module it is,
  what version of Perl on what OS, and sometimes what version of
  some relevent third library (like XML::Parser).  They reply,
  saying "Perl 5".  I say "I need the exact version, as reported
  by C<perl -v>".  They tell me.  And I say "I, uh, also asked about
  the version of my module and XML::Parser [or whatever]".  They say
  "Oh yeah.  It's 2.27".  "Is that my module or XML::Parser?"
  "XML::Parser."  "OK, and what about my module's
  version?"  "Ohyeah.  That's 3.11."  By this time, days have passed,
  and what should have been a simple operation -- reporting the version
  of Perl and relevent modules, has been needlessly complicated.

  This module is for simplifying that task.  If you add "use
  Module::Versions::Report;" to a program (especially handy if your
  program is one that demonstrates a bug in some module), then when the
  program has finished running, you well get a report detailing the all
  modules in memory, and noting the version of each (for modules that
  defined a C<$VERSION>, at least).


pkgId: 62305c0af3a8ca90f253ea8f71d0db5638a6aa97
name: local-perl-MogileFS-Client
arch: src
version: 1.08
epoch: 0
release: 1
summary: MogileFS-Client - MogileFS client library
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Brad Fitzpatrick <brad@danga.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MogileFS-Client-1.08-1.src.rpm
checksum_type: sha
description:
  This module is a client library for the MogileFS distributed file system. The class method 'new' creates a client object against a
  particular mogilefs tracker and domain. This object may then be used to store and retrieve content easily from MogileFS.


pkgId: c108344b48ffea4c603e07cb4d0863c5b5c7e681
name: local-perl-Moo
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Moo-0.009012-1.src.rpm
checksum_type: sha
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: 45f2588d87f1c46ff4e63ce224f1209a399a1b50
name: local-perl-Moo
arch: src
version: 1.003000
epoch: 0
release: 1
summary: Moo - Minimalist Object Orientation (with Moose compatibility)
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: S Trout cpanMSTROUT <mst@shadowcat.co.uk>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Moo-1.003000-1.src.rpm
checksum_type: sha
description:
  This module is an extremely light-weight subset of L<Moose> optimised for
  rapid startup and "pay only for what you use".

  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 L<Mouse> this module does not aim at full compatibility with
  L<Moose>'s surface syntax, preferring instead of provide full interoperability
  via the metaclass inflation capabilities described in L</MOO AND MOOSE>.

  For a full list of the minor differences between L<Moose> and L<Moo>'s surface
  syntax, see L</INCOMPATIBILITIES WITH MOOSE>.


pkgId: c08de0cec1798d3aafae0a99b13456bba8ecf576
name: local-perl-Moose
arch: src
version: 1.21
epoch: 0
release: 1
summary: Moose - A postmodern object system for Perl 5
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Moose is an open project, there are at this point dozens of people who have
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Moose-1.21-1.src.rpm
checksum_type: sha
description:
  Moose is an extension of the Perl 5 object system.

  The main goal of Moose is to make Perl 5 Object Oriented programming
  easier, more consistent and less tedious. With Moose you can to think
  more about what you want to do and less about the mechanics of OOP.

  Additionally, Moose is built on top of L<Class::MOP>, which is a
  metaclass system for Perl 5. This means that Moose not only makes
  building normal Perl 5 objects better, but it provides the power of
  metaclass programming as well.


pkgId: f4710ae6e55c2ef1d705ca5d72aa14e629f46dc7
name: local-perl-Moose
arch: src
version: 2.0104
epoch: 0
release: 1
summary: Moose - A postmodern object system for Perl 5
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Stevan Little <stevan@iinteractive.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Moose-2.0104-1.src.rpm
checksum_type: sha
description:
  Moose is an extension of the Perl 5 object system.

  The main goal of Moose is to make Perl 5 Object Oriented programming easier, more consistent, and less tedious. With Moose you can think more about what you want to do and less about the mechanics of OOP.

  Additionally, Moose is built on top of Class::MOP, which is a metaclass system for Perl 5. This means that Moose not only makes building normal Perl 5 objects better, but it provides the power of metaclass programming as well.


pkgId: 7b9968863178082f4d0bbfb8dfe3477f16441e3f
name: local-perl-MooseX-Aliases
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MooseX-Aliases-0.10-1.src.rpm
checksum_type: sha
rpm_vendor:
  Jesse Luehrs <doy at tozt dot net>, Chris Prather <chris@prather.org>, Justin Hunter <justin.d.hunter at gmail dot com>


pkgId: f8686a2838e69825112a8181712a012ea5b4cf3d
name: local-perl-MooseX-Role-Parameterized
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MooseX-Role-Parameterized-0.27-1.src.rpm
checksum_type: sha
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: d78e1b331ddaad5086576f7ee8d18c13bcd3406c
name: local-perl-MooseX-Types-DateTimeX
arch: src
version: 0.10
epoch: 0
release: 1
summary: MooseX-Types-DateTimeX - Extensions to L<MooseX::Types::DateTime::ButMaintained>
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: John Napiorkowski <jjn1056 at yahoo.com>, Evan Carroll <me@evancarroll.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-MooseX-Types-DateTimeX-0.10-1.src.rpm
checksum_type: sha
description:
  This module builds on L<MooseX::Types::DateTime> to add additional custom types and coercions.  Since it builds on an existing type, all coercions and constraints are inherited.

  The package name is left as is for legacy reasons: this module is really a Type with coercions for L<DateTimeX::Easy>. DateTimeX is just a namespace for non-core or less-official L<DateTime> modules.


pkgId: 68635372dd1631a46366007cd939dbf46a23c9bd
name: local-perl-Mouse
arch: src
version: 0.60
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Mouse-0.60-1.src.rpm
checksum_type: sha
description:
  L<Moose> is wonderful. B<Use Moose instead of Mouse.>

  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 L<HTTP::Engine> and FastCGI for the
  latter, if possible.

  Mouse aims to alleviate this by providing a subset of Moose's functionality,
  faster.

  We're also going as light on dependencies as possible. Mouse currently has
  B<no dependencies> except for testing modules.


pkgId: 91813f6a4987a5dc2f68cd5bf64bd6ff69c4783f
name: local-perl-Net-CIDR-Lite
arch: src
version: 0.20
epoch: 0
release: 1
summary: Net-CIDR-Lite - Perl extension for merging IPv4 or IPv6 CIDR addresses
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Douglas Wilson <dougw@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-CIDR-Lite-0.20-1.src.rpm
checksum_type: sha
description:
  Faster alternative to Net::CIDR when merging a large number
  of CIDR address ranges. Works for IPv4 and IPv6 addresses.


pkgId: 6c0293a11cf03842ce730071756812d0f10c3c32
name: local-perl-Net-DNS
arch: src
version: 0.63
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-DNS-0.63-1.src.rpm
checksum_type: sha
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: 5b92f029074297e979ff0deef9f3f0badba53a8a
name: local-perl-Net-FTPSSL
arch: src
version: 0.23
epoch: 0
release: 1
summary: Net-FTPSSL - A FTP over SSL/TLS class
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Curtis Leach <cleach at cpan dot org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-FTPSSL-0.23-1.src.rpm
checksum_type: sha
description:
  C<Net::FTPSSL> is a class implementing a simple FTP client over a Secure
  Sockets Layer (SSL) or Transport Layer Security (TLS) connection written in
  Perl as described in RFC959 and RFC2228.  It will use TLS by default.


pkgId: a26656254e022abec169da8ff5b4e56991478f2d
name: local-perl-Net-HTTPS-Any
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-HTTPS-Any-0.10-1.src.rpm
checksum_type: sha
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: 79d655071b99523a20f12c03ed2cbeea544d3092
name: local-perl-Net-IP
arch: src
version: 1.25
epoch: 0
release: 1
summary: Net-IP - Perl extension for manipulating IPv4/IPv6 addresses
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Manuel Valente <manuel.valente@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-IP-1.25-1.src.rpm
checksum_type: sha
description:
  This module provides functions to deal with B<IPv4/IPv6> addresses. The module
  can be used as a class, allowing the user to instantiate IP objects, which can
  be single IP addresses, prefixes, or ranges of addresses. There is also a
  procedural way of accessing most of the functions. Most subroutines can take
  either B<IPv4> or B<IPv6> addresses transparently.


pkgId: 39c7533008b59dca2c05ef4f70b152363bf6cf9d
name: local-perl-Net-IRC
arch: src
version: 0.75
epoch: 0
release: 1
summary: Net-IRC - Perl interface to the Internet Relay Chat protocol
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-IRC-0.75-1.src.rpm
checksum_type: sha
description:
  Welcome to Net::IRC, a work in progress. First intended to be a quick tool
  for writing an IRC script in Perl, Net::IRC has grown into a comprehensive
  Perl implementation of the IRC protocol (RFC 1459), developed by several
  members of the EFnet IRC channel #perl, and maintained in channel #net-irc.

  There are 4 component modules which make up Net::IRC:

  =over

  =item *

  Net::IRC

  The wrapper for everything else, containing methods to generate
  Connection objects (see below) and a connection manager which does an event
  loop on all available filehandles. Sockets or files which are readable (or
  writable, or whatever you want it to select() for) get passed to user-supplied
  handler subroutines in other packages or in user code.

  =item *

  Net::IRC::Connection

  The big time sink on this project. Each Connection instance is a
  single connection to an IRC server. The module itself contains methods for
  every single IRC command available to users (Net::IRC isn't designed for
  writing servers, for obvious reasons), methods to set, retrieve, and call
  handler functions which the user can set (more on this later), and too many
  cute comments. Hey, what can I say, we were bored.

  =item *

  Net::IRC::Event

  Kind of a struct-like object for storing info about things that the
  IRC server tells you (server responses, channel talk, joins and parts, et
  cetera). It records who initiated the event, who it affects, the event
  type, and any other arguments provided for that event. Incidentally, the
  only argument passed to a handler function.

  =item *

  Net::IRC::DCC

  The analogous object to Connection.pm for connecting, sending and
  retrieving with the DCC protocol. Instances of DCC.pm are invoked from
  C<Connection-E<gt>new_{send,get,chat}> in the same way that
  C<IRC-E<gt>newconn> invokes C<Connection-E<gt>new>. This will make more
  sense later, we promise.

  =back

  The central concept that Net::IRC is built around is that of handlers
  (or hooks, or callbacks, or whatever the heck you feel like calling them).
  We tried to make it a completely event-driven model, a la Tk -- for every
  conceivable type of event that your client might see on IRC, you can give
  your program a custom subroutine to call. But wait, there's more! There are
  3 levels of handler precedence:

  =over

  =item *

  Default handlers

  Considering that they're hardwired into Net::IRC, these won't do
  much more than the bare minimum needed to keep the client listening on the
  server, with an option to print (nicely formatted, of course) what it hears
  to whatever filehandles you specify (STDOUT by default). These get called
  only when the user hasn't defined any of his own handlers for this event.

  =item *

  User-definable global handlers

  The user can set up his own subroutines to replace the default
  actions for I<every> IRC connection managed by your program. These only get
  invoked if the user hasn't set up a per-connection handler for the same
  event.

  =item *

  User-definable per-connection handlers

  Simple: this tells a single connection what to do if it gets an event of
  this type. Supersedes global handlers if any are defined for this event.

  =back

  And even better, you can choose to call your custom handlers before
  or after the default handlers instead of replacing them, if you wish. In
  short, it's not perfect, but it's about as good as you can get and still be
  documentable, given the sometimes horrendous complexity of the IRC protocol.


pkgId: f1d0490baf5bd7d4218d0c54930c97001120f592
name: local-perl-Net-Ident
arch: src
version: 1.20
epoch: 0
release: 1
summary: Net-Ident - lookup the username on the remote end of a TCP/IP connection
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: JanPieter Cornet <johnpc@xs4all.nl>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-Ident-1.20-1.src.rpm
checksum_type: sha
description:
  You can either use the simple interface, which does one ident
  lookup at a time, or use the asynchronous interface to perform
  (possibly) many simultaneous lookups, or simply continue serving other
  things while the lookup is proceeding.


pkgId: 632cd8be043b30cad06a228cc4999ab60c246343
name: local-perl-Net-Jabber
arch: src
version: 2.0
epoch: 0
release: 1
summary: Net-Jabber - Jabber Perl Library
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ryan Eatmon <>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-Jabber-2.0-1.src.rpm
checksum_type: sha
description:
  Net::Jabber is a convenient tool to use for any perl script that would
    like to utilize the Jabber Instant Messaging protocol.  While not a
    client in and of itself, it provides all of the necessary back-end
    functions to make a CGI client or command-line perl client feasible and
    easy to use.  Net::Jabber is a wrapper around the rest of the official
    Net::Jabber::xxxxxx packages.

    There is are example scripts in the example directory that provide you
    with examples of very simple Jabber programs.


    NOTE: The parser that XML::Stream::Parser provides, as are most Perl
    parsers, is synchronous.  If you are in the middle of parsing a packet
    and call a user defined callback, the Parser is blocked until your
    callback finishes.  This means you cannot be operating on a packet,
    send out another packet and wait for a response to that packet.  It
    will never get to you.  Threading might solve this, but as of the
    writing of this, threading in Perl is not quite up to par yet.  This
    issue will be revisted in the future.


pkgId: f5606f142c676db053e748e55fbb995e38e2d992
name: local-perl-Net-LibIDN
arch: src
version: 0.10
epoch: 0
release: 1
summary: Net-LibIDN - Perl bindings for GNU Libidn
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Thomas Jacob <jacob@internet24.de>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-LibIDN-0.10-1.src.rpm
checksum_type: sha
description:
  Provides bindings for GNU Libidn, a C library for handling Internationalized
  Domain Names according to IDNA (RFC 3490), in a way very much inspired by
  Turbo Fredriksson's PHP-IDN.


pkgId: f96c81ef98ff67645b51c59e4ac260a5c410ae16
name: local-perl-Net-Pcap
arch: src
version: 0.16
epoch: 0
release: 1
summary: Net-Pcap - Interface to pcap(3) LBL packet capture library
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sebastien Aperghis-Tramoni <sebastien@aperghis.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-Pcap-0.16-1.src.rpm
checksum_type: sha
description:
  C<Net::Pcap> is a Perl binding to the LBL pcap(3) library.
  The README for libpcap describes itself as:

    "a system-independent interface for user-level packet capture.
    libpcap provides a portable framework for low-level network
    monitoring.  Applications include network statistics collection,
    security monitoring, network debugging, etc."


pkgId: ee7c8c41043212b69dd3e72defe465f78a056f04
name: local-perl-Net-SFTP
arch: src
version: 0.10
epoch: 0
release: 1
summary: Net-SFTP - Secure File Transfer Protocol client
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Dave Rolsky <autarch@urth.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-SFTP-0.10-1.src.rpm
checksum_type: sha
description:
  I<Net::SFTP> is a pure-Perl implementation of the Secure File
  Transfer Protocol (SFTP) - file transfer built on top of the
  SSH2 protocol. I<Net::SFTP> uses I<Net::SSH::Perl> to build a
  secure, encrypted tunnel through which files can be transferred
  and managed. It provides a subset of the commands listed in
  the SSH File Transfer Protocol IETF draft, which can be found
  at I<http://www.openssh.com/txt/draft-ietf-secsh-filexfer-00.txt>.

  SFTP stands for Secure File Transfer Protocol and is a method of
  transferring files between machines over a secure, encrypted
  connection (as opposed to regular FTP, which functions over an
  insecure connection). The security in SFTP comes through its
  integration with SSH, which provides an encrypted transport
  layer over which the SFTP commands are executed, and over which
  files can be transferred. The SFTP protocol defines a client
  and a server; only the client, not the server, is implemented
  in I<Net::SFTP>.

  Because it is built upon SSH, SFTP inherits all of the built-in
  functionality provided by I<Net::SSH::Perl>: encrypted
  communications between client and server, multiple supported
  authentication methods (eg. password, public key, etc.).


pkgId: 21cb709b3d2e1e36d164f2fdd550f81ceaf32816
name: local-perl-Net-SFTP-Foreign
arch: src
version: 1.63_06
epoch: 0
release: 1
summary: Net-SFTP-Foreign - Secure File Transfer Protocol client
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Salvador Fandino <sfandino@yahoo.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-SFTP-Foreign-1.63_06-1.src.rpm
checksum_type: sha
description:
  SFTP stands for SSH File Transfer Protocol and is a method of
  transferring files between machines over a secure, encrypted
  connection (as opposed to regular FTP, which functions over an
  insecure connection). The security in SFTP comes through its
  integration with SSH, which provides an encrypted transport layer over
  which the SFTP commands are executed.

  Net::SFTP::Foreign is a Perl client for the SFTP version 3 as defined
  in the SSH File Transfer Protocol IETF draft, which can be found at
  L<http://www.openssh.org/txt/draft-ietf-secsh-filexfer-02.txt> (also
  included on this package distribution, on the C<rfc> directory).

  Net::SFTP::Foreign uses any compatible C<ssh> command installed on
  the system (for instance, OpenSSH C<ssh>) to establish the secure
  connection to the remote server.

  A wrapper module L<Net::SFTP::Foreign::Compat> is also provided for
  compatibility with L<Net::SFTP>.


pkgId: 415ae7089224e31d3cff2ff936cc151e2630d935
name: local-perl-Net-SSH-Perl
arch: src
version: 1.30
epoch: 0
release: 1
summary: Net-SSH-Perl - Perl client interface to SSH
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: David Robins <dbrobins@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-SSH-Perl-1.30-1.src.rpm
checksum_type: sha
description:
  I<Net::SSH::Perl> is an all-Perl module implementing an SSH
  (Secure Shell) client. It is compatible with both the SSH-1 and
  SSH-2 protocols.

  I<Net::SSH::Perl> enables you to simply and securely execute commands
  on remote machines, and receive the STDOUT, STDERR, and exit status
  of that remote command. It contains built-in support for various
  methods of authenticating with the server (password authentication,
  RSA challenge-response authentication, etc.). It completely implements
  the I/O buffering, packet transport, and user authentication layers
  of the SSH protocol, and makes use of external Perl libraries (in
  the Crypt:: family of modules) to handle encryption of all data sent
  across the insecure network. It can also read your existing SSH
  configuration files (F</etc/ssh_config>, etc.), RSA identity files,
  DSA identity files, known hosts files, etc.

  One advantage to using I<Net::SSH::Perl> over wrapper-style
  implementations of ssh clients is that it saves on process
  overhead: you no longer need to fork and execute a separate process
  in order to connect to an sshd. Depending on the amount of time
  and memory needed to fork a process, this win can be quite
  substantial; particularly if you're running in a persistent
  Perl environment (I<mod_perl>, for example), where forking a new
  process is a drain on process and memory resources.

  It also simplifies the process of using password-based authentications;
  when writing a wrapper around I<ssh> you probably need to use
  I<Expect> to control the ssh client and give it your password.
  I<Net::SSH::Perl> has built-in support for the authentication
  protocols, so there's no longer any hassle of communicating with
  any external processes.

  The SSH2 protocol support (present in I<Net::SSH::Perl> as of version
  1.00) is compatible with the SSH2 implementation in OpenSSH, and should
  also be fully compatible with the "official" SSH implementation. If
  you find an SSH2 implementation that is not compatible with
  I<Net::SSH::Perl>, please let me know (email address down in
  I<AUTHOR & COPYRIGHTS>); it turns out that some SSH2 implementations
  have subtle differences from others. 3DES (C<3des-cbc>), Blowfish
  (C<blowfish-cbc>), and RC4 (C<arcfour>) ciphers are currently
  supported for SSH2 encryption, and integrity checking is performed
  by either the C<hmac-sha1> or C<hmac-md5> algorithms. Compression, if
  requested, is limited to Zlib. Supported server host key algorithms
  are C<ssh-dss> (the default) and C<ssh-rsa> (requires I<Crypt::RSA>);
  supported SSH2 public key authentication algorithms are the same.

  If you're looking for SFTP support, take a look at I<Net::SFTP>,
  which provides a full-featured Perl implementation of SFTP, and
  sits on top of I<Net::SSH::Perl>. SFTP requires the usage of the
  SSH2 protocol.


pkgId: 17db60bbf01b62c65a28bea85b2462e6fb93a65a
name: local-perl-Net-Server
arch: src
version: 0.97
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-Server-0.97-1.src.rpm
checksum_type: sha
description:
  C<Net::Server> is an extensible, generic Perl server engine.
  C<Net::Server> combines the good properties from
  C<Net::Daemon> (0.34), C<NetServer::Generic> (1.03), and
  C<Net::FTPServer> (1.0), and also from various concepts in
  the Apache Webserver.

  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.

  C<Net::Server> uses ideologies of C<Net::FTPServer> in order
  to provide extensibility.  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: 0d89f665c42ac7bfa2c04dc750e32596540c1425
name: local-perl-Net-Server-Mail
arch: src
version: 0.17
epoch: 0
release: 1
summary: Net-Server-Mail - Class to easily create a mail server
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Olivier Poitrey <rs@rhapsodyk.net>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-Server-Mail-0.17-1.src.rpm
checksum_type: sha
description:
  This module is a versatile and extensible implementation of the SMTP
  protocol and its different evolutions like ESMTP and LMTP. The event
  driven object-oriented API makes easy to incorporate the SMTP protocol
  to your programs.

  Other SMTPd implementations don't support useful ESMTP extensions and
  the LMTP protocol. Their interface design precludes adding them
  later. So I've decided to rewrite a complete implementation with
  extensibility in mind.

  It provides mechanism to easy addition future or not yet implemented
  ESMTP extensions. Developers can hook code at each SMTP session state
  and change the module's behaviors by registering event call-backs. The
  class is designed to be easily inherited from.

  This class is the base class for mail service protocols such axs
  B<Net::Server::Mail::SMTP>, B<Net::Server::Mail::ESMTP> and
  B<Net::Server::Mail::LMTP>. Refer to the documentation provided with
  each of these modules.


pkgId: 0a80cdf08fab3692f3508d50a7fa3c1419fda1c7
name: local-perl-Net-Telnet
arch: src
version: 3.03
epoch: 0
release: 1
summary: Net-Telnet - Interact with TELNET port or other TCP ports
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jay Rogers <jay@rgrs.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-Telnet-3.03-1.src.rpm
checksum_type: sha
description:
  Net::Telnet allows you to make client connections to a TCP port and do
  network I/O, especially to a port using the TELNET protocol.  Simple
  I/O methods such as print, get, and getline are provided.  More
  sophisticated interactive features are provided because connecting to
  a TELNET port ultimately means communicating with a program designed
  for human interaction.  These interactive features include the ability
  to specify a time-out and to wait for patterns to appear in the input
  stream, such as the prompt from a shell.

  Other reasons to use this module than strictly with a TELNET port are:

  =over 2

  =item *

  You're not familiar with sockets and you want a simple way to make
  client connections to TCP services.

  =item *

  You want to be able to specify your own time-out while connecting,
  reading, or writing.

  =item *

  You're communicating with an interactive program at the other end of
  some socket or pipe and you want to wait for certain patterns to
  appear.

  =back

  Here's an example that prints who's logged-on to the remote host
  sparky.  In addition to a username and password, you must also know
  the user's shell prompt, which for this example is C<bash$>

      use Net::Telnet ();
      $t = new Net::Telnet (Timeout => 10,
                            Prompt => '/bash\$ $/');
      $t->open("sparky");
      $t->login($username, $passwd);
      @lines = $t->cmd("who");
      print @lines;

  More examples are in the B<EXAMPLES> section below.

  Usage questions should be directed to the Usenet newsgroup
  comp.lang.perl.modules.

  Contact me, Jay Rogers <jay@rgrs.com>, if you find any bugs or have
  suggestions for improvement.


pkgId: 0e3af4a380218a76e0fbcb071352b09adc982808
name: local-perl-Net-UPS
arch: src
version: 0.04
epoch: 0
release: 1
summary: Net-UPS - Implementation of UPS Online Tools API in Perl
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sherzod B. Ruzmetov <sherzodr@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Net-UPS-0.04-1.src.rpm
checksum_type: sha
description:
  Net::UPS implements UPS' Online Tools API in Perl. In a nutshell, Net::UPS knows how to retrieve rates and service information for shipping packages using UPS, as well as for validating U.S. addresses.

  This manual is optimized to be used as a quick reference. If you're knew to Net::UPS, and this manual doesn't seem to help, you're encouraged to read L<Net::UPS::Tutorial|Net::UPS::Tutorial> first.


pkgId: ad503fbc43f05b859889ac0c6acb815b9c49e83e
name: local-perl-NetAddr-IP
arch: src
version: 4.007
epoch: 0
release: 1
summary: NetAddr-IP - Manages IPv4 and IPv6 addresses and subnets
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Luis E. Muñoz <luismunoz@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-NetAddr-IP-4.007-1.src.rpm
checksum_type: sha
description:
  This module provides an object-oriented abstraction on top of IP
  addresses or IP subnets, that allows for easy manipulations.
  Version 4.xx of NetAdder::IP will will work older
  versions of Perl and does B<not> use Math::BigInt as in previous versions.

  The internal representation of all IP objects is in 128 bit IPv6 notation.
  IPv4 and IPv6 objects may be freely mixed.


pkgId: 21b0ab88736f4fc6950b60a59113ffc8706fde4d
name: local-perl-Number-Compare
arch: src
version: 0.01
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Number-Compare-0.01-1.src.rpm
checksum_type: sha
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: b631021954fc44ab46c29060a19f6a55df72beb5
name: local-perl-Number-Format
arch: src
version: 1.73
epoch: 0
release: 1
summary: Number-Format - Perl extension for formatting numbers
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: William R. Ward <wrw@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Number-Format-1.73-1.src.rpm
checksum_type: sha
description:
  These functions provide an easy means of formatting numbers in a
  manner suitable for displaying to the user.

  There are two ways to use this package.  One is to declare an object
  of type Number::Format, which you can think of as a formatting engine.
  The various functions defined here are provided as object methods.
  The constructor C<new()> can be used to set the parameters of the
  formatting engine.  Valid parameters are:

    THOUSANDS_SEP     - character inserted between groups of 3 digits
    DECIMAL_POINT     - character separating integer and fractional parts
    MON_THOUSANDS_SEP - like THOUSANDS_SEP, but used for format_price
    MON_DECIMAL_POINT - like DECIMAL_POINT, but used for format_price
    INT_CURR_SYMBOL   - character(s) denoting currency (see format_price())
    DECIMAL_DIGITS    - number of digits to the right of dec point (def 2)
    DECIMAL_FILL      - boolean; whether to add zeroes to fill out decimal
    NEG_FORMAT        - format to display negative numbers (def ``-x'')
    KILO_SUFFIX       - suffix to add when format_bytes formats kilobytes (trad)
    MEGA_SUFFIX       -    "    "  "    "        "         "    megabytes (trad)
    GIGA_SUFFIX       -    "    "  "    "        "         "    gigabytes (trad)
    KIBI_SUFFIX       - suffix to add when format_bytes formats kibibytes (iec)
    MEBI_SUFFIX       -    "    "  "    "        "         "    mebibytes (iec)
    GIBI_SUFFIX       -    "    "  "    "        "         "    gibibytes (iec)

  They may be specified in upper or lower case, with or without a
  leading hyphen ( - ).

  If C<THOUSANDS_SEP> is set to the empty string, format_number will not
  insert any separators.

  The defaults for C<THOUSANDS_SEP>, C<DECIMAL_POINT>,
  C<MON_THOUSANDS_SEP>, C<MON_DECIMAL_POINT>, and C<INT_CURR_SYMBOL>
  come from the POSIX locale information (see L<perllocale>).  If your
  POSIX locale does not provide C<MON_THOUSANDS_SEP> and/or
  C<MON_DECIMAL_POINT> fields, then the C<THOUSANDS_SEP> and/or
  C<DECIMAL_POINT> values are used for those parameters.  Formerly,
  POSIX was optional but this caused problems in some cases, so it is
  now required.  If this causes you hardship, please contact the author
  of this package at <SwPrAwM@cpan.org> (remove "SPAM" to get correct
  email address) for help.

  If any of the above parameters are not specified when you invoke
  C<new()>, then the values are taken from package global variables of
  the same name (e.g.  C<$DECIMAL_POINT> is the default for the
  C<DECIMAL_POINT> parameter).  If you use the C<:vars> keyword on your
  C<use Number::Format> line (see non-object-oriented example below) you
  will import those variables into your namesapce and can assign values
  as if they were your own local variables.  The default values for all
  the parameters are:

    THOUSANDS_SEP     = ','
    DECIMAL_POINT     = '.'
    MON_THOUSANDS_SEP = ','
    MON_DECIMAL_POINT = '.'
    INT_CURR_SYMBOL   = 'USD'
    DECIMAL_DIGITS    = 2
    DECIMAL_FILL      = 0
    NEG_FORMAT        = '-x'
    KILO_SUFFIX       = 'K'
    MEGA_SUFFIX       = 'M'
    GIGA_SUFFIX       = 'G'
    KIBI_SUFFIX       = 'KiB'
    MEBI_SUFFIX       = 'MiB'
    GIBI_SUFFIX       = 'GiB'

  Note however that when you first call one of the functions in this
  module I<without> using the object-oriented interface, further setting
  of those global variables will have no effect on non-OO calls.  It is
  recommended that you use the object-oriented interface instead for
  fewer headaches and a cleaner design.

  The C<DECIMAL_FILL> and C<DECIMAL_DIGITS> values are not set by the
  Locale system, but are definable by the user.  They affect the output
  of C<format_number()>.  Setting C<DECIMAL_DIGITS> is like giving that
  value as the C<$precision> argument to that function.  Setting
  C<DECIMAL_FILL> to a true value causes C<format_number()> to append
  zeroes to the right of the decimal digits until the length is the
  specified number of digits.

  C<NEG_FORMAT> is only used by C<format_negative()> and is a string
  containing the letter 'x', where that letter will be replaced by a
  positive representation of the number being passed to that function.
  C<format_number()> and C<format_price()> utilize this feature by
  calling C<format_negative()> if the number was less than 0.

  C<KILO_SUFFIX>, C<MEGA_SUFFIX>, and C<GIGA_SUFFIX> are used by
  C<format_bytes()> when the value is over 1024, 1024*1024, or
  1024*1024*1024, respectively.  The default values are "K", "M", and
  "G".  These apply in the default "traditional" mode only.  Note: TERA
  or higher are not implemented because of integer overflows on 32-bit
  systems.

  C<KIBI_SUFFIX>, C<MEBI_SUFFIX>, and C<GIBI_SUFFIX> are used by
  C<format_bytes()> when the value is over 1024, 1024*1024, or
  1024*1024*1024, respectively.  The default values are "KiB", "MiB",
  and "GiB".  These apply in the "iso60027"" mode only.  Note: TEBI or
  higher are not implemented because of integer overflows on 32-bit
  systems.

  The only restrictions on C<DECIMAL_POINT> and C<THOUSANDS_SEP> are that
  they must not be digits, must not be identical, and must each be one
  character.  There are no restrictions on C<INT_CURR_SYMBOL>.

  For example, a German user might include this in their code:

    use Number::Format;
    my $de = new Number::Format(-thousands_sep   => '.',
                                -decimal_point   => ',',
                                -int_curr_symbol => 'DEM');
    my $formatted = $de->format_number($number);

  Or, if you prefer not to use the object oriented interface, you can do
  this instead:

    use Number::Format qw(:subs :vars);
    $THOUSANDS_SEP   = '.';
    $DECIMAL_POINT   = ',';
    $INT_CURR_SYMBOL = 'DEM';
    my $formatted = format_number($number);


pkgId: eeffa57d706527ce70455b6dea371f7fd048c3e5
name: local-perl-OLE-Storage_Lite
arch: src
version: 0.17
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-OLE-Storage_Lite-0.17-1.src.rpm
checksum_type: sha
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: 65ebfc1a83a46ae561dfe949412b18e4db9baaea
name: local-perl-PAR-Dist
arch: src
version: 0.31
epoch: 0
release: 1
summary: PAR-Dist - Create and manipulate PAR distributions
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Audrey Tang <cpan@audreyt.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-PAR-Dist-0.31-1.src.rpm
checksum_type: sha
description:
  This module creates and manipulates I<PAR distributions>.  They are
  architecture-specific B<PAR> files, containing everything under F<blib/>
  of CPAN distributions after their C<make> or C<Build> stage, a
  F<META.yml> describing metadata of the original CPAN distribution,
  and a F<MANIFEST> detailing all files within it.  Digitally signed PAR
  distributions will also contain a F<SIGNATURE> file.

  The naming convention for such distributions is:

      $NAME-$VERSION-$ARCH-$PERL_VERSION.par

  For example, C<PAR-Dist-0.01-i386-freebsd-5.8.0.par> corresponds to the
  0.01 release of C<PAR-Dist> on CPAN, built for perl 5.8.0 running on
  C<i386-freebsd>.


pkgId: 483d89a594ac7e4b5ce4042e6515c15c5efaed46
name: local-perl-PDF-Reuse
arch: src
version: 0.35
epoch: 0
release: 1
summary: PDF-Reuse - Reuse and mass produce PDF documents
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Lars Lundberg LARSLUND@CPAN.ORG
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-PDF-Reuse-0.35-1.src.rpm
checksum_type: sha
description:
  This module could be used when you want to mass produce similar (but not identical)
  PDF documents and reuse templates, JavaScripts and some other components. It is
  functional to be fast, and to give your programs capacity to produce many pages
  per second and very big PDF documents if necessary.

  The module produces PDF-1.4 files. Some features of PDF-1.5, like "object streams"
  and "cross reference streams", are supported, but only at an experimental level. More
  testing is needed. (If you get problems with a new document from Acrobat 6 or higher, try to
  save it or recreate it as a PDF-1.4 document first, before using it together with
  this module.)

  =over 2

  =item Templates

  Use your favorite program, probably a commercial visual tool, to produce single
  PDF-files to be used as templates, and then use this module to B<mass produce> files
  from them.

  (If you want small PDF-files or want special graphics, you can use this module also,
  but visual tools are often most practical.)

  =item Lists

  The module uses "XObjects" extensively. This is a format that makes it possible
  create big lists, which are compact at the same time.


  =item PDF-operators

  The module gives you a good possibility to program at a "low level" with the basic
  graphic operators of PDF, if that is what you want to do. You can build your
  own libraries of low level routines, with PDF-directives "controlled" by Perl.

  =item Archive-format

  If you want, you get your new documents logged in a format suitable for archiving
  or transfer.


  PDF::Reuse::Tutorial might show you best what you can do with this module.

  =item JavaScript

  You can attach JavaScripts to your PDF-files.

  You can have libraries of JavaScripts. No cutting or pasting, and those who include
  the scripts in documents only need to know how to initiate them. (Of course those
  who write the scripts have to know Acrobat JavaScript well.)

  =back


pkgId: 90ac0da167e60caabed2ab76b437fd82d661095a
name: local-perl-PDF-Table
arch: src
version: 0.9.3
epoch: 0
release: 1
summary: PDF-Table - A utility class for building table layouts in a PDF::API2 object.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Desislav Kamenov <desi@vratza.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-PDF-Table-0.9.3-1.src.rpm
checksum_type: sha
description:
  This class is a utility for use with the PDF::API2 module from CPAN.
  It can be used to display text data in a table layout within the PDF.
  The text data must be in a 2d array (such as returned by a DBI statement handle fetchall_arrayref() call).
  The PDF::Table will automatically add as many new pages as necessary to display all of the data.
  Various layout properties, such as font, font size, and cell padding and background color can be specified for each column and/or for even/odd rows.
  Also a (non)repeated header row with different layout properties can be specified.

  See the METHODS section for complete documentation of every parameter.


pkgId: 3471b09ada379a6d38806a7ef1ccd991b0933e25
name: local-perl-PHP-Serialization
arch: src
version: 0.29
epoch: 0
release: 1
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jesse Brown <jbrown@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-PHP-Serialization-0.29-1.src.rpm
checksum_type: sha
summary:
  PHP-Serialization - simple flexible means of converting the output of PHP's serialize() into the equivalent Perl memory structure, and vice versa.

description:
  Provides a simple, quick means of serializing perl memory structures (including object data!) into a format that PHP can deserialize() and access, and vice versa.

  NOTE: Converts PHP arrays into Perl Arrays when the PHP array used exclusively numeric indexes, and into Perl Hashes then the PHP array did not.


pkgId: 8509397e2d65d9082615fa0fa5e4d6b1a30ad35d
name: local-perl-POE
arch: src
version: 1.003
epoch: 0
release: 1
summary: POE - A portable networking and multitasking framework.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Rocco Caputo <rcaputo@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-POE-1.003-1.src.rpm
checksum_type: sha
description:
  POE is a framework for cooperative, event driven multitasking and
  networking in Perl.  Other languages have similar frameworks.  Python
  has Twisted.  TCL has "the event loop".

  POE originally was developed as the core of a persistent object server
  and runtime environment.  It has since evolved into something much
  more generic and widely useful.

  POE provides a unified interface for several other event loops,
  including select(), L<IO::Poll|IO::Poll>, L<Glib>, L<Gtk>, L<Tk>, L<Wx>,
  L<Gtk2>, and so on.
  Check the CPAN for the full list of L<POE::Loop|POE::Loop> modules.

  POE is designed in layers, each building atop the lower level ones.
  Programs are free to use POE at any level of abstraction, and
  different levels can be mixed and matched seamlessly within a single
  program.

  POE's bundled abstraction layers are the tip of a growing iceberg.
  L<Sprocket>, L<POE::Stage|POE::Stage>, and other CPAN distributions build upon this
  work.  You're encouraged to look around.

  No matter how high you go, though, it all boils down to calls to
  L<POE::Kernel|POE::Kernel>.  So your down-to-earth code can easily cooperate
  with stratospheric systems.


pkgId: 919d6b33fa82bfeef43023a1714882132ab89a25
name: local-perl-POE-Component-Server-HTTP
arch: src
version: 0.09
epoch: 0
release: 1
summary: POE-Component-Server-HTTP - Foundation of a POE HTTP Daemon
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Arthur Bergman
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-POE-Component-Server-HTTP-0.09-1.src.rpm
checksum_type: sha
description:
  POE::Component::Server::HTTP (PoCo::HTTPD) is a framework for building
  custom HTTP servers based on POE. It is loosely modeled on the ideas of
  apache and the mod_perl/Apache module.

  It is built alot on work done by Gisle Aas on HTTP::* modules and the URI
  module which are subclassed.

  PoCo::HTTPD lets you register different handler, stacked by directory that
  will be run during the cause of the request.


pkgId: 54e97191c3350791d753fa0e2ae5735ffa95f70d
name: local-perl-POE-Test-Loops
arch: src
version: 1.002
epoch: 0
release: 1
summary: POE-Test-Loops - POE::Loop test suite
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Rocco Caputo <rcaputo@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-POE-Test-Loops-1.002-1.src.rpm
checksum_type: sha
description:
  POE::Test::Loops contains one function, generate(), which will
  generate all the loop tests for one or more POE::Loop subclasses.

  The L</SYNOPSIS> example is a version of L<poe-gen-tests>, which is a
  stand-alone utility to generate the actual tests.  L<poe-gen-tests>
  also documents the POE::Test::Loops system in more detail.


pkgId: 3a40ac4942b69b027f91f8b5f28068fcece36b97
name: local-perl-PadWalker
arch: src
version: 1.7
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-PadWalker-1.7-1.src.rpm
checksum_type: sha
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 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: f198d20f50098891cde93acb43c5fbfcfb0e07b5
name: local-perl-Params-Check
arch: src
version: 0.32
epoch: 0
release: 1
summary: Params-Check - Templated based param validation
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jos Boumans <kane[at]cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Params-Check-0.32-1.src.rpm
checksum_type: sha
description:
  Params::Check is a generic input parsing/checking mechanism.

  It allows you to validate input via a template. The only requirement
  is that the arguments must be named.

  Params::Check can do the following things for you:

  =over 4

  =item *

  Convert all keys to lowercase

  =item *

  Check if all required arguments have been provided

  =item *

  Set arguments that have not been provided to the default

  =item *

  Weed out arguments that are not supported and warn about them to the
  user

  =item *

  Validate the arguments given by the user based on strings, regexes,
  lists or even subroutines

  =item *

  Enforce type integrity if required

  =back

  Most of Params::Check's power comes from its template, which we'll
  discuss below:


pkgId: b520f665ef4a59f31376f9a24c9c04c726b08589
name: local-perl-Params-Util
arch: src
version: 1.03
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Params-Util-1.03-1.src.rpm
checksum_type: sha
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: 0e537ebdb1284181cad48a463a1db9cb0ecff7ba
name: local-perl-Params-Validate
arch: src
version: 0.91
epoch: 0
release: 1
summary: Params-Validate - Validate method/function parameters
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Dave Rolsky, <autarch@urth.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Params-Validate-0.91-1.src.rpm
checksum_type: sha
description:
  The Params::Validate module allows you to validate method or function
  call parameters to an arbitrary level of specificity.  At the simplest
  level, it is capable of validating the required parameters were given
  and that no unspecified additional parameters were passed in.

  It is also capable of determining that a parameter is of a specific
  type, that it is an object of a certain class hierarchy, that it
  possesses certain methods, or applying validation callbacks to
  arguments.


pkgId: 79573f4a18c72d4cf673cbc3066004e4b6a9eee9
name: local-perl-Parse-CPAN-Meta
arch: src
version: 1.4401
epoch: 0
release: 1
summary: Parse-CPAN-Meta - Parse META.yml and META.json CPAN metadata files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Adam Kennedy <adamk@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Parse-CPAN-Meta-1.4401-1.src.rpm
checksum_type: sha
description:
  B<Parse::CPAN::Meta> is a parser for F<META.json> and F<META.yml> files, using
  L<JSON::PP> and/or L<CPAN::Meta::YAML>.

  B<Parse::CPAN::Meta> provides three methods: C<load_file>, C<load_json_string>,
  and C<load_yaml_string>.  These will read and deserialize CPAN metafiles, and
  are described below in detail.

  B<Parse::CPAN::Meta> provides a legacy API of only two functions,
  based on the YAML functions of the same name. Wherever possible,
  identical calling semantics are used.  These may only be used with YAML sources.

  All error reporting is done with exceptions (die'ing).

  Note that META files are expected to be in UTF-8 encoding, only.  When
  converted string data, it must first be decoded from UTF-8.


pkgId: 904601fe165c6119cf6f8db928aff7110f2488c9
name: local-perl-Perl-Critic-Nits
arch: src
version: v1.0.0
epoch: 0
release: 1
summary: Perl-Critic-Nits - policies of nits I like to pick.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Kent Cowgill <kent@c2group.net>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Perl-Critic-Nits-v1.0.0-1.src.rpm
checksum_type: sha
description:
  The included policy is:

  =over

  =item L<Perl::Critic::Policy::ValuesAndExpressions::ProhibitAccessOfPrivateData>

  Prohibits direct access to a hash-based object's hash. [Severity: 5]

  =back


pkgId: 846003d67a9616eebe0c7dd7bf25562fa193620e
name: local-perl-Perl-Tidy
arch: src
version: 20071205
epoch: 0
release: 1
summary: Perl-Tidy - indent and reformat perl scripts
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Steve Hancock <perltidy@perltidy.sourceforge.net>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Perl-Tidy-20071205-1.src.rpm
checksum_type: sha
description:
  This module makes the functionality of the perltidy utility available to perl
  scripts.  Any or all of the input parameters may be omitted, in which case the
  @ARGV array will be used to provide input parameters as described
  in the perltidy(1) man page.

  For example, the perltidy script is basically just this:

      use Perl::Tidy;
      Perl::Tidy::perltidy();

  The module accepts input and output streams by a variety of methods.
  The following list of parameters may be any of a the following: a
  filename, an ARRAY reference, a SCALAR reference, or an object with
  either a B<getline> or B<print> method, as appropriate.

          source            - the source of the script to be formatted
          destination       - the destination of the formatted output
          stderr            - standard error output
          perltidyrc        - the .perltidyrc file
          logfile           - the .LOG file stream, if any
          errorfile         - the .ERR file stream, if any
          dump_options      - ref to a hash to receive parameters (see below),
          dump_options_type - controls contents of dump_options
          dump_getopt_flags - ref to a hash to receive Getopt flags
          dump_options_category - ref to a hash giving category of options
          dump_abbreviations    - ref to a hash giving all abbreviations

  The following chart illustrates the logic used to decide how to
  treat a parameter.

     ref($param)  $param is assumed to be:
     -----------  ---------------------
     undef        a filename
     SCALAR       ref to string
     ARRAY        ref to array
     (other)      object with getline (if source) or print method

  If the parameter is an object, and the object has a B<close> method, that
  close method will be called at the end of the stream.

  =over 4

  =item source

  If the B<source> parameter is given, it defines the source of the
  input stream.

  =item destination

  If the B<destination> parameter is given, it will be used to define the
  file or memory location to receive output of perltidy.

  =item stderr

  The B<stderr> parameter allows the calling program to capture the output
  to what would otherwise go to the standard error output device.

  =item perltidyrc

  If the B<perltidyrc> file is given, it will be used instead of any
  F<.perltidyrc> configuration file that would otherwise be used.

  =item argv

  If the B<argv> parameter is given, it will be used instead of the
  B<@ARGV> array.  The B<argv> parameter may be a string, a reference to a
  string, or a reference to an array.  If it is a string or reference to a
  string, it will be parsed into an array of items just as if it were a
  command line string.

  =item dump_options

  If the B<dump_options> parameter is given, it must be the reference to a hash.
  In this case, the parameters contained in any perltidyrc configuration file
  will be placed in this hash and perltidy will return immediately.  This is
  equivalent to running perltidy with --dump-options, except that the perameters
  are returned in a hash rather than dumped to standard output.  Also, by default
  only the parameters in the perltidyrc file are returned, but this can be
  changed (see the next parameter).  This parameter provides a convenient method
  for external programs to read a perltidyrc file.  An example program using
  this feature, F<perltidyrc_dump.pl>, is included in the distribution.

  Any combination of the B<dump_> parameters may be used together.

  =item dump_options_type

  This parameter is a string which can be used to control the parameters placed
  in the hash reference supplied by B<dump_options>.  The possible values are
  'perltidyrc' (default) and 'full'.  The 'full' parameter causes both the
  default options plus any options found in a perltidyrc file to be returned.

  =item dump_getopt_flags

  If the B<dump_getopt_flags> parameter is given, it must be the reference to a
  hash.  This hash will receive all of the parameters that perltidy understands
  and flags that are passed to Getopt::Long.  This parameter may be
  used alone or with the B<dump_options> flag.  Perltidy will
  exit immediately after filling this hash.  See the demo program
  F<perltidyrc_dump.pl> for example usage.

  =item dump_options_category

  If the B<dump_options_category> parameter is given, it must be the reference to a
  hash.  This hash will receive a hash with keys equal to all long parameter names
  and values equal to the title of the corresponding section of the perltidy manual.
  See the demo program F<perltidyrc_dump.pl> for example usage.

  =item dump_abbreviations

  If the B<dump_abbreviations> parameter is given, it must be the reference to a
  hash.  This hash will receive all abbreviations used by Perl::Tidy.  See the
  demo program F<perltidyrc_dump.pl> for example usage.

  =back


pkgId: ae72dfbe64238f44ab3f3f2b6fd04f48e6dabd58
name: local-perl-Plack
arch: src
version: 0.9988
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Plack-0.9988-1.src.rpm
checksum_type: sha
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: dd6bf0ae689f708f4a273b6118ce6e123dec1049
name: local-perl-Pod-Coverage
arch: src
version: 0.19
epoch: 0
release: 3
summary: Checks if the documentation of a module is comprehensive
url: http://search.cpan.org/dist/Pod-Coverage/
rpm_license: GPL+ or Artistic
rpm_group: Development/Libraries
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: local-perl-Pod-Coverage-0.19-3.src.rpm
checksum_type: sha
description:
  Developers hate writing documentation.  They'd hate it even more if their
  computer tattled on them, but maybe they'll be even more thankful in the
  long run.  Even if not, perlmodstyle tells you to, so you must obey.

  This module provides a mechanism for determining if the pod for a given
  module is comprehensive.


pkgId: 9ed57b35d7650ecdb5c958358e94af97fa89d9fc
name: local-perl-Pod-Escapes
arch: src
version: 1.04
epoch: 0
release: 1
summary: Pod-Escapes - - for resolving Pod E<...> sequences
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sean M Burke <Csburke@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Pod-Escapes-1.04-1.src.rpm
checksum_type: sha
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.

  By default, Pod::Escapes exports none of its symbols.  But
  you can request any of them to be exported.
  Either request them individually, as with
  "use Pod::Escapes qw(symbolname symbolname2...);",
  or you can do "use Pod::Escapes qw(:ALL);" to get all
  exportable symbols.


pkgId: a70e6c836591bd0062d4cb97baf29ca6c79e332c
name: local-perl-Pod-POM
arch: src
version: 0.17
epoch: 0
release: 1
summary: Pod-POM - POD Object Model
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Wardley <abw@kfs.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Pod-POM-0.17-1.src.rpm
checksum_type: sha
description:
  This module implements a parser to convert Pod documents into a simple
  object model form known hereafter as the Pod Object Model.  The object
  model is generated as a hierarchical tree of nodes, each of which
  represents a different element of the original document.  The tree can
  be walked manually and the nodes examined, printed or otherwise
  manipulated.  In addition, Pod::POM supports and provides view objects
  which can automatically traverse the tree, or section thereof, and
  generate an output representation in one form or another.

  Let's look at a typical Pod document by way of example.


pkgId: 035a87208cba4c69ef7fe2139acdafc05f1c2a63
name: local-perl-Pod-Readme
arch: src
version: 0.11
epoch: 0
release: 1
summary: Pod-Readme - Convert POD to README file
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: David Precious <davidp@preshweb.co.uk>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Pod-Readme-0.11-1.src.rpm
checksum_type: sha
description:
  This module is a subclass of L<Pod::PlainText> which provides additional
  POD markup for generating F<README> files.

  Why should one bother with this? One can simply use

    pod2text Module.pm > README

  A problem with doing that is that the default L<pod2text> converter will
  add text to links, so that "LZ<><Module>" is translated to
  "the Module manpage".

  Another problem is that the F<README> includes the entirety of
  the module documentation!  Most people browsing the F<README> file do not
  need all of this information.

  Likewise, including installation and requirement information in the
  module documentation is not necessary either, since the module is already
  installed.

  This module allows authors to mark portions of the POD to be included only
  in, or to be excluded from the F<README> file.  It also allows you to
  include portions of another file (such as a separate F<ChangeLog>).

  =begin readme

  See the module documentation for more details.

  =end readme

  =for readme stop


pkgId: 71b6d845b211747dfb694909f8a6f3a6eae391f6
name: local-perl-Pod-Spell
arch: src
version: 1.01
epoch: 0
release: 1
summary: Pod-Spell - - a formatter for spellchecking Pod
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sean M Burke <Csburke@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Pod-Spell-1.01-1.src.rpm
checksum_type: sha
description:
  Pod::Spell is a Pod formatter whose output is good for
  spellchecking.  Pod::Spell rather like L<Pod::Text|Pod::Text>, except that
  it doesn't put much effort into actual formatting, and it suppresses things
  that look like Perl symbols or Perl jargon (so that your spellchecking
  program won't complain about mystery words like "C<$thing>"
  or "C<Foo::Bar>" or "hashref").

  This class provides no new public methods.  All methods of interest are
  inherited from L<Pod::Parser|Pod::Parser> (which see).  The especially
  interesting ones are C<parse_from_filehandle> (which without arguments
  takes from STDIN and sends to STDOUT) and C<parse_from_file>.  But you
  can probably just make do with the examples in the synopsis though.

  This class works by filtering out words that look like Perl or any
  form of computerese (like "C<$thing>" or "C<NE<gt>7>" or
  "C<@{$foo}{'bar','baz'}>", anything in CE<lt>...E<gt> or FE<lt>...E<gt>
  codes, anything in verbatim paragraphs (codeblocks), and anything
  in the stopword list.  The default stopword list for a document starts
  out from the stopword list defined by L<Pod::Wordlist|Pod::Wordlist>,
  and can be supplemented (on a per-document basis) by having
  C<"=for stopwords"> / C<"=for :stopwords"> region(s) in a document.


pkgId: 0b2e9cb593e2ee78da0a69491b571253bc28bc79
name: local-perl-PostScript-Simple
arch: src
version: 0.07
epoch: 0
release: 1
summary: PostScript-Simple - Produce PostScript files from Perl
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Matthew Newton <mcnewton@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-PostScript-Simple-0.07-1.src.rpm
checksum_type: sha
description:
  PostScript::Simple allows you to have a simple method of writing PostScript
  files from Perl. It has graphics primitives that allow lines, curves, circles,
  polygons and boxes to be drawn. Text can be added to the page using standard
  PostScript fonts.

  The images can be single page EPS files, or multipage PostScript files. The
  image size can be set by using a recognised paper size ("C<A4>", for example) or
  by giving dimensions. The units used can be specified ("C<mm>" or "C<in>", etc)
  and are the same as those used in TeX. The default unit is a bp, or a PostScript
  point, unlike TeX.


pkgId: 4c6c395590f213f7fad7b723deee4d83621c3177
name: local-perl-Proc-Daemon
arch: src
version: 0.03
epoch: 0
release: 1
summary: Proc-Daemon - Run Perl program as a daemon process
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Earl Hood <earl@earlhood.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Proc-Daemon-0.03-1.src.rpm
checksum_type: sha
description:
  This module contains the routine B<Init> which can be called by
  a Perl program to initialize itself as a daemon.  A daemon is a
  process that runs in the background with no controlling terminal.
  Generally servers (like FTP and HTTP servers) run as daemon processes.
  Note, do not make the mistake that a daemon == server.

  The B<Proc::Daemon::Init> function does the following:

  =over 4

  =item 1

  Forks a child and exits the parent process.

  =item 2

  Becomes a session leader (which detaches the program from
  the controlling terminal).

  =item 3

  Forks another child process and exits first child.  This prevents
  the potential of acquiring a controlling terminal.

  =item 4

  Changes the current working directory to "/".

  =item 5

  Clears the file creation mask.

  =item 6

  Closes all open file descriptors.

  =back

  You will notice that no logging facility, or other functionality
  is performed.  B<Proc::Daemon::Init> just performs the main steps
  to initialize a program as daemon.  Since other funtionality can vary
  depending on the nature of the program, B<Proc::Daemon> leaves
  the implementation of other desired functionality to the
  caller, or other module/library (like B<Sys::Syslog>).

  There is no meaningful return value B<Proc::Daemon::Init>.  If an
  error occurs in B<Init> so it cannot perform the above steps, than
  it croaks with an error message.  One can prevent program termination
  by using eval.


pkgId: db963a0a682e615810c4d13e5ed07da37051682b
name: local-perl-Proc-PID-File
arch: src
version: 1.24
epoch: 0
release: 1
summary: Proc-PID-File - A module to manage PID files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Erick Calder <ecalder@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Proc-PID-File-1.24-1.src.rpm
checksum_type: sha
description:
  This Perl module is useful for writers of daemons and other processes that need to tell whether they are already running, in order to prevent multiple process instances.  The module accomplishes this via *nix-style I<pidfiles>, which are files that store a process identifier.


pkgId: 65768a4309bd9b04e3e4449789b440ccdc486c93
name: local-perl-Proc-ProcessTable
arch: src
version: 0.45
epoch: 0
release: 1
summary: Perl interface to the UNIX process table
url: http://search.cpan.org/dist/Proc-ProcessTable/
rpm_license: Artistic/GPL
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Dag Wieers <dag@wieers.com>
location_href: local-perl-Proc-ProcessTable-0.45-1.src.rpm
checksum_type: sha
description:
  This module is a first crack at providing a consistent interface to
  Unix (and maybe other multitasking OS's) process table information.
  The impetus for this came about with my frustration at having to parse
  the output of various systems' ps commands to check whether specific
  processes were running on different boxes at a larged mixed UNIX site.
  The output format of ps was different on each OS, and sometimes
  changed with each new release of an OS. Also, running a ps subprocess
  from within a perl or shell script and parsing the output was not a
  very efficient or aesthetic way to do things.


pkgId: ce62994397a72f460c05299c399f313fab67d972
name: local-perl-Readonly
arch: src
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Readonly-1.03-1.src.rpm
checksum_type: sha
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: 0ccce0a6a9b0ff0c30f9d3cd99b008c8c84539a7
name: local-perl-Readonly-XS
arch: src
version: 1.04
epoch: 0
release: 1
summary: Readonly-XS - Companion module for Readonly.pm, to speed up read-only
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Eric Roode <roode@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Readonly-XS-1.04-1.src.rpm
checksum_type: sha
description:
  The Readonly module (q.v.) is an effective way to create
  non-modifiable variables.  However, it's relatively slow.

  The reason it's slow is that is implements the read-only-ness of
  variables via tied objects.  This mechanism is inherently slow.  Perl
  simply has to do a lot of work under the hood to make tied variables
  work.

  This module corrects the speed problem, at least with respect to
  scalar variables.  When Readonly::XS is installed, Readonly uses it to
  access the internals of scalar variables.  Instead of creating a
  scalar variable object and tying it, Readonly simply flips the
  SvREADONLY bit in the scalar's FLAGS structure.

  Readonly arrays and hashes are not sped up by this, since the
  SvREADONLY flag only works for scalars.  Arrays and hashes always use
  the tie interface.

  Why implement this as a separate module?  Because not everyone can use
  XS.  Not everyone has a C compiler.  Also, installations with a
  statically-linked perl may not want to recompile their perl binary
  just for this module.  Rather than render Readonly.pm useless for
   these people, the XS portion was put into a separate module.

  Programs that you write do not need to know whether Readonly::XS is
  installed or not.  They should just "use Readonly" and let Readonly
  worry about whether or not it can use XS.  If the Readonly::XS is
  present, Readonly will be faster.  If not, it won't.  Either way, it
  will still work, and your code will not have to change.

  Your program can check whether Readonly.pm is using XS or not by
  examining the $Readonly::XSokay variable.  It will be true if the
  XS module was found and is being used.  Please do not change this
  variable.


pkgId: 96ca04282c636f18f2076bf36e022d6125f7876b
name: local-perl-Regexp-Common
arch: src
version: 2.122
epoch: 0
release: 1
summary: Regexp-Common - Provide commonly requested regular expressions
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Damian Conway <damian@conway.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Regexp-Common-2.122-1.src.rpm
checksum_type: sha
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: d3608ec4092005095d7c87eb82aeef1c3df11220
name: local-perl-Regexp-Common-profanity_us
arch: src
version: 2.2
epoch: 0
release: 1
summary: Regexp-Common-profanity_us - - provide regexes for U.S. profanity
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: T. M. Brannon <tbone@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Regexp-Common-profanity_us-2.2-1.src.rpm
checksum_type: sha
description:
  use Regexp::Common qw /profanity_us/;

    my $RE = $RE{profanity}{us}{normal}{label}{-keep}{-dist=>3};

    while (<>) {
        warn "PROFANE" if /$RE/;
    }

  Or easier

   use Regexp::Profanity::US;

   $profane = profane     ($string);
   @profane = profane_list($string);


pkgId: a0ea02d0b62e7c9899b9635a11db9a3dc0a2a4d0
name: local-perl-Regexp-Match-Any
arch: src
version: 0.03
epoch: 0
release: 1
summary: Regexp-Match-Any - Yet another Regexp Module
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Scott McWhirter <scott@kungfuftr.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Regexp-Match-Any-0.03-1.src.rpm
checksum_type: sha
description:
  This module allows you to pass the match_any() function a reference to an array of regexes which will
    then return a full regex for the the variable to be matched against. Optionally, you can pass it
    matching arguements such as 'g' or 'i'. Pass these in one variable with no spaces.
    Note: I from personal experience have found this module to be very handy for use with Mail::Audit.


pkgId: 9f505963b3274c971d4f48715e7446bbdfdb177d
name: local-perl-Regexp-Parser
arch: src
version: 0.20
epoch: 0
release: 1
summary: Regexp-Parser - base class for parsing regexes
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jeff japhy Pinyan <japhy@perlmonk.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Regexp-Parser-0.20-1.src.rpm
checksum_type: sha
description:
  This module parses regular expressions (regexes).  Its default "grammar"
  is Perl 5.8.4's regex set.  Grammar is quoted because the module does
  not so much define a grammar as let each matched node state what it
  expects to match next, but there is not currently a way of extracting a
  complete grammar.  This may change in future versions.

  This module is designed as a replacement (though not drop-in) for my old
  F<YAPE::Regex> modules.


pkgId: 284a61f32e2f45a2d2c8afd7f3aff0dc1e3da2b7
name: local-perl-Rose-DB
arch: src
version: 0.744
epoch: 0
release: 1
summary: Rose-DB - A DBI wrapper and abstraction layer.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: John C Siracusa <siracusa@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Rose-DB-0.744-1.src.rpm
checksum_type: sha
description:
  L<Rose::DB> is a wrapper and abstraction layer for L<DBI>-related functionality.  A L<Rose::DB> object "has a" L<DBI> object; it is not a subclass of L<DBI>.

  Please see the L<tutorial|Rose::DB::Tutorial> (perldoc Rose::DB::Tutorial) for an example usage scenario that reflects "best practices" for this module.

  B<Tip:> Are you looking for an object-relational mapper (ORM)?  If so, please see the L<Rose::DB::Object> module.  L<Rose::DB::Object> is an ORM that uses this module to manage its database connections.  L<Rose::DB> alone is simply a data source abstraction layer; it is not an ORM.


pkgId: 690baa607e03dbfe838b247dbfbea91addb2b4ed
name: local-perl-Rose-DB-Object
arch: src
version: 0.770
epoch: 0
release: 1
summary: Rose-DB-Object - Extensible, high performance object-relational mapper (ORM).
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: John C Siracusa <siracusa@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Rose-DB-Object-0.770-1.src.rpm
checksum_type: sha
description:
  L<Rose::DB::Object> is a base class for objects that encapsulate a single row in a database table.  L<Rose::DB::Object>-derived objects are sometimes simply called "L<Rose::DB::Object> objects" in this documentation for the sake of brevity, but be assured that derivation is the only reasonable way to use this class.

  L<Rose::DB::Object> inherits from, and follows the conventions of, L<Rose::Object>.  See the L<Rose::Object> documentation for more information.

  For an informal overview of this module distribution, consult the L<Rose::DB::Object::Tutorial>.


pkgId: a07ee0798fb188e91a0aa9d973d5f519ce9a0b6d
name: local-perl-Rose-DBx-AutoReconnect
arch: src
version: 0.02
epoch: 0
release: 1
summary: Rose-DBx-AutoReconnect - Rose::DB with auto-reconnect to server
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Peter Karman <karman@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Rose-DBx-AutoReconnect-0.02-1.src.rpm
checksum_type: sha
description:
  Rose::DBx::AutoReconnect is a subclass of Rose::DB. Additional features
  include:

  =over

  =item

  If using new_or_cached() method, will ping() dbh on every fetch from
  cache to ensure that the dbh is connected. This extends
  the basic Rose::DB::Cache behaviour beyond mod_perl/Apache::DBI.

  =item

  Convenient logger() method for debugging.

  =item

  Always uses DBI connect_cached() method when creating handles.

  =back

  Rose::DBx::AutoReconnect was written to allow new_or_cached() to
  work with MySQL's "morning bug" and to allow for restarting
  your database without restarting your application.
  See also Rose::DBx::Cache::Anywhere.


pkgId: 6bef2dd701f6b17a7a9e35b727e55a0a0b66dd48
name: local-perl-Rose-DBx-Object-Cached-CHI
arch: src
version: 0.14
epoch: 0
release: 1
summary: Rose-DBx-Object-Cached-CHI - Rose::DB::Object Cache using the CHI interface
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Kevin C. McGrath (kmcgrath@baknet.com)
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Rose-DBx-Object-Cached-CHI-0.14-1.src.rpm
checksum_type: sha
description:
  This module intends to extend the caching ability in Rose::DB::Object
  allowing objects to be cached by any driver that can be used with
  the CHI interface. This opens the possibility to cache objects across
  scripts or even servers by opening up methods of caching such as
  FastMmap and memcached.

  Most of the code is taken straight from L<Rose::DB::Object::Cached>.
  This does not extend Rose::DB::Object::Cached because function calls and
  how the cache is accessed needed to be changed thoughout the code.


pkgId: db2fdde572e68673aeed78fa27375baf117c158e
name: local-perl-Rose-DateTime
arch: src
version: 0.532
epoch: 0
release: 1
summary: Rose-DateTime - DateTime helper functions and objects.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: John C Siracusa <siracusa@mindspring.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Rose-DateTime-0.532-1.src.rpm
checksum_type: sha
description:
  The C<Rose::DateTime::*> modules provide a few convenience functions and objects for use with C<DateTime> dates.

  L<Rose::DateTime::Util> contains a simple date parser and a slightly customized date formatter.

  L<Rose::DateTime::Parser> encapsulates a date parser with an associated default time zone.

  This module (C<Rose::DateTime>) exists mostly to provide a version number for CPAN.  See the individual modules for some actual documentation.


pkgId: 4ba69aa05609f818595d32a3456461e26762d941
name: local-perl-Rose-Object
arch: src
version: 0.853
epoch: 0
release: 1
summary: Rose-Object - A simple object base class.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: John C Siracusa <siracusa@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Rose-Object-0.853-1.src.rpm
checksum_type: sha
description:
  L<Rose::Object> is a generic object base class.  It provides very little
  functionality, but a healthy dose of convention.


pkgId: 647f2fad5a1a1737edd167b891f2c5c7066bbe51
name: local-perl-SOAP-Lite
arch: src
version: 0.710.08
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-SOAP-Lite-0.710.08-1.src.rpm
checksum_type: sha
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: 11ccb9f365f5cdecc89afb45671a50644860859a
name: local-perl-SQL-Abstract
arch: src
version: 1.72
epoch: 0
release: 1
summary: SQL-Abstract - Generate SQL from Perl data structures
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Nathan Wiger <nate@wiger.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-SQL-Abstract-1.72-1.src.rpm
checksum_type: sha
description:
  This module was inspired by the excellent L<DBIx::Abstract>.
  However, in using that module I found that what I really wanted
  to do was generate SQL, but still retain complete control over my
  statement handles and use the DBI interface. So, I set out to
  create an abstract SQL generation module.

  While based on the concepts used by L<DBIx::Abstract>, there are
  several important differences, especially when it comes to WHERE
  clauses. I have modified the concepts used to make the SQL easier
  to generate from Perl data structures and, IMO, more intuitive.
  The underlying idea is for this module to do what you mean, based
  on the data structures you provide it. The big advantage is that
  you don't have to modify your code every time your data changes,
  as this module figures it out.

  To begin with, an SQL INSERT is as easy as just specifying a hash
  of C<key=value> pairs:

      my %data = (
          name => 'Jimbo Bobson',
          phone => '123-456-7890',
          address => '42 Sister Lane',
          city => 'St. Louis',
          state => 'Louisiana',
      );

  The SQL can then be generated with this:

      my($stmt, @bind) = $sql->insert('people', \%data);

  Which would give you something like this:

      $stmt = "INSERT INTO people
                      (address, city, name, phone, state)
                      VALUES (?, ?, ?, ?, ?)";
      @bind = ('42 Sister Lane', 'St. Louis', 'Jimbo Bobson',
               '123-456-7890', 'Louisiana');

  These are then used directly in your DBI code:

      my $sth = $dbh->prepare($stmt);
      $sth->execute(@bind);


pkgId: 5981297459584b8281c287ef63b0d467c2363b9a
name: local-perl-SQL-Statement
arch: src
version: 0.1021
epoch: 0
release: 1
summary: SQL-Statement - SQL parsing and processing engine
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jochen Wiedmann (joe@ispsoft.de)
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-SQL-Statement-0.1021-1.src.rpm
checksum_type: sha
description:
  For installing the module, see L<"INSTALLATION"> below.

  The SQL::Statement module implements a small, abstract SQL engine. This
  module is not usefull itself, but as a base class for deriving concrete
  SQL engines. The implementation is designed to work fine with the
  DBI driver DBD::CSV, thus probably not so well suited for a larger
  environment, but I'd hope it is extendable without too much problems.

  By parsing an SQL query you create an SQL::Statement instance. This
  instance offers methods for retrieving syntax, for WHERE clause and
  statement evaluation.


pkgId: 168352ba0d805ed02a38c2d88ebef510e05fd4ba
name: local-perl-SQL-Statement
arch: src
version: 1.15
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)
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-SQL-Statement-1.15-1.src.rpm
checksum_type: sha
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, complexly 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 persistant 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: 505c0574382f2cfe443b5ffb0b5c7b4918d79410
name: local-perl-Safe-Hole
arch: src
version: 0.10
epoch: 0
release: 1
summary: Safe-Hole - make a hole to the original main compartment in the Safe compartment
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sey Nakajima <Eltnakajima@netstock.co.jpEgt,>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Safe-Hole-0.10-1.src.rpm
checksum_type: sha
description:
  We can call outside defined subroutines from the Safe compartment
  using share(), or can call methods through the object that is copied
  into the Safe compartment using varglob(). But that subroutines or
  methods are executed in the Safe compartment too, so they cannot call
  another subroutines that are dinamically qualified with the package
  name such as class methods nor can they compile code that uses opcodes
  that are forbidden within the compartment.

    Through Safe::Hole, we can execute outside defined subroutines in the
  original main compartment from the Safe compartment.

    Note that if a subroutine called through Safe::Hole::call does a
  Carp::croak() it will report the error as having occured within
  Safe::Hole.  This can be avoided by including Safe::Hole::User in the
  @ISA for the package containing the subroutine.


pkgId: 4495649cfd55291dec92b392ae575491c2676666
name: local-perl-Schedule-At
arch: src
version: 1.15
epoch: 0
release: 1
summary: Schedule-At - OS independent interface to the Unix 'at' command
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jose A Rodriguez <jose AT rodriguez.jp>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Schedule-At-1.15-1.src.rpm
checksum_type: sha
description:
  This modules provides an OS independent interface to 'at', the Unix
  command that allows you to execute commands at a specified time.

  =over 4

  =item Schedule::At::add

  Adds a new job to the at queue.

  You have to specify a B<TIME> and a command to execute. The B<TIME> has
  a common format: YYYYMMDDHHmm where B<YYYY> is the year (4 digits), B<MM>
  the month (01-12), B<DD> is the day (01-31), B<HH> the hour (00-23) and
  B<mm> the minutes.

  The command is passed with the B<COMMAND> or the B<FILE> parameter.
  B<COMMAND> can be used to pass the command as an string, or an array of
  commands, and B<FILE> to read the commands from a file.

  The optional parameter B<TAG> serves as an application specific way to
  identify a job or a set of jobs.

  Returns 0 on success or a value != 0 if an error occurred.

  =item Schedule::At::readJobs

  Read the job content identified by the B<JOBID> or B<TAG> parameters.

  Returns a hash of JOBID => $string where $string is the the job
  content. As the operating systems usually add a few environment settings,
  the content is longer than the command provided when adding the job.

  =item Schedule::At::remove

  Remove an at job.

  You identify the job to be deleted using the B<JOBID> parameter (an
  opaque string returned by the getJobs subroutine). You can also specify
  a job or a set of jobs to delete with the B<TAG> parameter, removing
  all the jobs that have the same tag (as specified with the add subroutine).

  Used with JOBID, returns 0 on success or a value != 0 if an error occurred.
  Used with TAG, returns a hash reference where the keys are the JOBID of
  the jobs found and the values indicate the success of the remove operation.

  =item Schedule::At::getJobs

  Called with no params returns a hash with all the current jobs or
  dies if an error has occurred.
  It's possible to specify the B<TAG> or B<JOBID> parameters so only matching
  jobs are returned.
  For each job the key is a JOBID (an OS dependent string that shouldn't be
  interpreted), and the value is a hash reference.

  This hash reference points to a hash with the keys:

  =over 4

  =item TIME

  An OS dependent string specifying the time to execute the command

  =item TAG

  The tag specified in the Schedule::At::add subroutine

  =back

  =back


pkgId: 39f46931a49a689a55ed21ca7d247dc4b30cf118
name: local-perl-Scope-Guard
arch: src
version: 0.03
epoch: 0
release: 1
summary: Scope-Guard - lexically scoped resource management
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: chocolateboy <chocolate.boy@email.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Scope-Guard-0.03-1.src.rpm
checksum_type: sha
description:
  This module provides a convenient way to perform cleanup or other forms of resource
  management at the end of a scope. It is particularly useful when dealing with exceptions:
  the Scope::Guard constructor takes a reference to a subroutine that is guaranteed to
  be called even if the thread of execution is aborted prematurely. This effectively allows
  lexically-scoped "promises" to be made that are automatically honoured by perl's garbage
  collector.

  For more information, see: L<http://www.cuj.com/documents/s=8000/cujcexp1812alexandr/>


pkgId: b8aa5a4f58e8c423771fdadeaf06e9fc54f69fab
name: local-perl-Set-Crontab
arch: src
version: 1.02
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Set-Crontab-1.02-1.src.rpm
checksum_type: sha
description:
  Set::Crontab parses crontab-style lists of integers and defines some
  utility functions to make it easier to deal with them.


pkgId: 5f2ddc4d4402958a495d6f5f448b7e2dbbc34409
name: local-perl-Set-Infinite
arch: src
version: 0.63
epoch: 0
release: 1
summary: Set-Infinite - Infinite Sets math
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Flavio S. Glock <fglock@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Set-Infinite-0.63-1.src.rpm
checksum_type: sha
description:
  Set::Infinite is a Set Theory module for infinite sets.

  A set is a collection of objects.
  The objects that belong to a set are called its members, or "elements".

  As objects we allow (almost) anything:  reals, integers, and objects (such as dates).

  We allow sets to be infinite.

  There is no account for the order of elements. For example, {1,2} = {2,1}.

  There is no account for repetition of elements. For example, {1,2,2} = {1,1,1,2} = {1,2}.


pkgId: f518e86551aa790b2783bc83a4b9e76879528ab4
name: local-perl-ShadowHash
arch: src
version: 0.07
epoch: 0
release: 1
summary: 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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-ShadowHash-0.07-1.src.rpm
checksum_type: sha
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 "text", which takes a filename 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).

  You can call the add() method of the underlying object to add data sources
  to the shadow hash.  It takes the same arguments as the initial tie() does
  and interprets them in the same way.


pkgId: 217dcbe8c3ac7a1b26ddbddbdbb11a30479d36bb
name: local-perl-Socket6
arch: src
version: 0.22
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Socket6-0.22-1.src.rpm
checksum_type: sha
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: f5d6d158842fcea0e60dbbe75c465b3aa39d3725
name: local-perl-Sort-Versions
arch: src
version: 1.5
epoch: 0
release: 1
summary: Sort-Versions - a perl 5 module for sorting of revision-like numbers
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ed Avis <ed@membled.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Sort-Versions-1.5-1.src.rpm
checksum_type: sha
description:
  Sort::Versions allows easy sorting of mixed non-numeric and numeric strings,
  like the 'version numbers' that many shared library systems and revision
  control packages use. This is quite useful if you are trying to deal with
  shared libraries. It can also be applied to applications that intersperse
  variable-width numeric fields within text. Other applications can
  undoubtedly be found.

  For an explanation of the algorithm, itE<39>s simplest to look at these examples:

    1.1   <  1.2
    1.1a  <  1.2
    1.1   <  1.1.1
    1.1   <  1.1a
    1.1.a <  1.1a
    1     <  a
    a     <  b
    1     <  2
    1.1-3 <  1.1-4
    1.1-5 <  1.1.6

  More precisely (but less comprehensibly), the two strings are treated
  as subunits delimited by periods or hyphens. Each subunit can contain
  any number of groups of digits or non-digits. If digit groups are
  being compared on both sides, a numeric comparison is used, otherwise
  a ASCII ordering is used. A group or subgroup with more units will win
  if all comparisons are equal.  A period binds digit groups together
  more tightly than a hyphen.

  Some packages use a different style of version numbering: a simple
  real number written as a decimal. Sort::Versions has limited support
  for this style: when comparing two subunits which are both digit
  groups, if either subunit has a leading zero, then both are treated
  like digits after a decimal point. So for example:

    0002  <  1
    1.06  <  1.5

  This wonE<39>t always work, because there wonE<39>t always be a leading zero
  in real-number style version numbers. There is no way for
  Sort::Versions to know which style was intended. But a lot of the time
  it will do the right thing. If you are making up version numbers, the
  style with (possibly) more than one dot is the style to use.


pkgId: 9934f49812c7c4032da2fe2d5331b1cb46816467
name: local-perl-Sphinx-Search
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Sphinx-Search-0.27.2-1.src.rpm
checksum_type: sha
description:
  This is the Perl API client for the Sphinx open-source SQL full-text indexing
  search engine, L<http://www.sphinxsearch.com>.


pkgId: d94b27fe0f43667c516d63629cc3f278a22c5f45
name: local-perl-Spreadsheet-ParseExcel
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Spreadsheet-ParseExcel-0.59-1.src.rpm
checksum_type: sha
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: 647d38e7fe79223f26710dbd48bef56295f4687d
name: local-perl-Spreadsheet-WriteExcel
arch: src
version: 2.22
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Spreadsheet-WriteExcel-2.22-1.src.rpm
checksum_type: sha
description:
  The Spreadsheet::WriteExcel 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 and images can be written to the cells.

  The Excel file produced by this module is compatible with 97, 2000, 2002 and 2003.

  The module will work on the majority of Windows, UNIX and Macintosh 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: ba33f59470e2e20a2c21d218c6fe9568b8ad951e
name: local-perl-Spreadsheet-WriteExcel-Simple
arch: src
version: 1.04
epoch: 0
release: 1
summary: Spreadsheet-WriteExcel-Simple - A simple single-sheet Excel document
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tony Bowden <kasei@tmtm.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Spreadsheet-WriteExcel-Simple-1.04-1.src.rpm
checksum_type: sha
description:
  This provides an abstraction to the L<Spreadsheet::WriteExcel> module
  for easier creation of simple single-sheet Excel documents.

  In its most basic form it provides two methods for writing data:
  write_row and write_bold_row which write the data supplied to
  the next row of the spreadsheet.

  However, you can also use $ss->book and $ss->sheet to get at the
  underlying workbook and worksheet from Spreadsheet::WriteExcel if you
  wish to manipulate these directly.


pkgId: 62fd5eca533c239561644edb16347954369c0732
name: local-perl-Statistics-Descriptive
arch: src
version: 2.6
epoch: 0
release: 1
summary: Statistics-Descriptive - Supplies statistical methods for perl5
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Colin Kuskie (ckuskie@cadence.com)
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Statistics-Descriptive-2.6-1.src.rpm
checksum_type: sha
description:
  This module provides basic functions used in descriptive statistics.
  It has an object oriented design and supports two different types of
  data storage and calculation objects: sparse and full. With the sparse
  method, none of the data is stored and only a few statistical measures
  are available. Using the full method, the entire data set is retained
  and additional functions are available.

  Whenever a division by zero may occur, the denominator is checked to be
  greater than the value C<$Statistics::Descriptive::Tolerance>, which
  defaults to 0.0. You may want to change this value to some small
  positive value such as 1e-24 in order to obtain error messages in case
  of very small denominators.

  Many of the methods (both Sparse and Full) cache values so that subsequent
  calls with the same arguments are faster.


pkgId: 8561efadb9c171e71f388f30702ceee63fe76c84
name: local-perl-Statistics-Distributions
arch: src
version: 1.02
epoch: 0
release: 1
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Michael Kospach <mike.perl@gmx.at>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Statistics-Distributions-1.02-1.src.rpm
checksum_type: sha
summary:
  Statistics-Distributions - Perl module for calculating critical values and upper probabilities of common statistical distributions

description:
  This Perl module calculates percentage points (5 significant digits) of the u (standard normal) distribution, the student's t distribution, the chi-square distribution and the F distribution. It can also calculate the upper probability (5 significant digits) of the u (standard normal), the chi-square, the t and the F distribution.
  These critical values are needed to perform statistical tests, like the u test, the t test, the F test and the chi-squared test, and to calculate confidence intervals.

  If you are interested in more precise algorithms you could look at:
   StatLib: http://lib.stat.cmu.edu/apstat/ ;
   Applied Statistics Algorithms by Griffiths, P. and Hill, I.D., Ellis Horwood: Chichester (1985)


pkgId: 60b443028a853b6527f16da81bd524b9bddaf7f2
name: local-perl-Storable
arch: src
version: 2.18
epoch: 0
release: 1
summary: Storable - persistence for Perl data structures
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: by Raphael Manfredi <FEltRaphael_Manfredi@pobox.comEgt>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Storable-2.18-1.src.rpm
checksum_type: sha
description:
  The Storable package brings persistence to your Perl data structures
  containing SCALAR, ARRAY, HASH or REF objects, i.e. anything that can be
  conveniently stored to disk and retrieved at a later time.

  It can be used in the regular procedural way by calling "store" with
  a reference to the object to be stored, along with the file name where
  the image should be written.

  The routine returns "undef" for I/O problems or other internal error,
  a true value otherwise. Serious errors are propagated as a "die" exception.

  To retrieve data stored to disk, use "retrieve" with a file name.
  The objects stored into that file are recreated into memory for you,
  and a *reference* to the root object is returned. In case an I/O error
  occurs while reading, "undef" is returned instead. Other serious
  errors are propagated via "die".

  Since storage is performed recursively, you might want to stuff references
  to objects that share a lot of common data into a single array or hash
  table, and then store that object. That way, when you retrieve back the
  whole thing, the objects will continue to share what they originally shared.

  At the cost of a slight header overhead, you may store to an already
  opened file descriptor using the "store_fd" routine, and retrieve
  from a file via "fd_retrieve". Those names aren't imported by default,
  so you will have to do that explicitly if you need those routines.
  The file descriptor you supply must be already opened, for read
  if you're going to retrieve and for write if you wish to store.

  	store_fd(\%table, *STDOUT) || die "can't store to stdout\n";
  	$hashref = fd_retrieve(*STDIN);

  You can also store data in network order to allow easy sharing across
  multiple platforms, or when storing on a socket known to be remotely
  connected. The routines to call have an initial "n" prefix for *network*,
  as in "nstore" and "nstore_fd". At retrieval time, your data will be
  correctly restored so you don't have to know whether you're restoring
  from native or network ordered data.  Double values are stored stringified
  to ensure portability as well, at the slight risk of loosing some precision
  in the last decimals.

  When using "fd_retrieve", objects are retrieved in sequence, one
  object (i.e. one recursive tree) per associated "store_fd".

  If you're more from the object-oriented camp, you can inherit from
  Storable and directly store your objects by invoking "store" as
  a method. The fact that the root of the to-be-stored tree is a
  blessed reference (i.e. an object) is special-cased so that the
  retrieve does not provide a reference to that object but rather the
  blessed object reference itself. (Otherwise, you'd get a reference
  to that blessed object).


pkgId: 02f3733bd383b18e0df1db79edd1d681a697cc9b
name: local-perl-String-Format
arch: src
version: 1.14
epoch: 0
release: 1
summary: String-Format - sprintf-like string formatting capabilities with
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: darren@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-String-Format-1.14-1.src.rpm
checksum_type: sha
description:
  String::Format lets you define arbitrary printf-like format sequences
  to be expanded.  This module would be most useful in configuration
  files and reporting tools, where the results of a query need to be
  formatted in a particular way.  It was inspired by mutt's index_format
  and related directives (see <URL:http://www.mutt.org/doc/manual/manual-6.html#index_format>).


pkgId: 0e804c421bc000845e953122816f07229b017386
name: local-perl-Sub-Exporter-Progressive
arch: src
version: 0.001010
epoch: 0
release: 1
summary: Sub-Exporter-Progressive - Only use Sub::Exporter if you need it
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Axel Schmidt cpanFREW <frioux+cpan@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Sub-Exporter-Progressive-0.001010-1.src.rpm
checksum_type: sha
description:
  L<Sub::Exporter> is an incredibly powerful module, but with that power comes
  great responsibility, er- as well as some runtime penalties.  This module
  is a C<Sub::Exporter> wrapper that will let your users just use L<Exporter>
  if all they are doing is picking exports, but use C<Sub::Exporter> if your
  users try to use C<Sub::Exporter>'s more advanced features features, like
  renaming exports, if they try to use them.

  Note that this module will export C<@EXPORT>, C<@EXPORT_OK> and
  C<%EXPORT_TAGS> package variables for C<Exporter> to work.  Additionally, if
  your package uses advanced C<Sub::Exporter> features like currying, this module
  will only ever use C<Sub::Exporter>, so you might as well use it directly.


pkgId: 5447615771064c805396254131c3b32496a7598e
name: local-perl-Sub-Identify
arch: src
version: 0.03
epoch: 0
release: 1
summary: Sub-Identify - Retrieve names of code references
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: rgarcia@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Sub-Identify-0.03-1.src.rpm
checksum_type: sha
description:
  C<Sub::Identify> allows you to retrieve the real name of code references. For
  this, it uses perl's introspection mechanism, provided by the C<B> module.

  It provides four functions : C<sub_name> returns the name of the
  subroutine (or C<__ANON__> if it's an anonymous code reference),
  C<stash_name> returns its package, and C<sub_fullname> returns the
  concatenation of the two.

  The fourth function, C<get_code_info>, returns a list of two elements,
  the package and the subroutine name (in case of you want both and are worried
  by the speed.)

  In case of subroutine aliasing, those functions always return the
  original name.


pkgId: 020a54a96725f8fdcfa44c38e1b86584df005d76
name: local-perl-Sub-Install
arch: src
version: 0.924
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Sub-Install-0.924-1.src.rpm
checksum_type: sha
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: 9577cbfe1c5120112889f2e7f31082798cb5796c
name: local-perl-Sys-Syslog
arch: src
version: 0.33
epoch: 0
release: 1
summary: Sys-Syslog - Perl interface to the UNIX syslog(3) calls
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sebastien Aperghis-Tramoni <sebastien@aperghis.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Sys-Syslog-0.33-1.src.rpm
checksum_type: sha
description:
  C<Sys::Syslog> is an interface to the UNIX C<syslog(3)> program.
  Call C<syslog()> with a string priority and a list of C<printf()> args
  just like C<syslog(3)>.


pkgId: 619890d65bd6874433635a948d65a13f86ce50f7
name: local-perl-Sys-Utmp
arch: src
version: 1.7
epoch: 0
release: 1
summary: Sys-Utmp - Object(ish) Interface to UTMP files.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jonathan Stowe <jns@gellyfish.co.uk>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Sys-Utmp-1.7-1.src.rpm
checksum_type: sha
description:
  Sys::Utmp provides a vaguely object oriented interface to the Unix user
  accounting file ( sometimes /etc/utmp or /var/run/utmp).  Whilst it would
  prefer to use the getutent() function from the systems C libraries it
  will attempt to provide its own if they are missing.

  This may not be the module that you are looking for - there is a User::Utmp
  which provides a different procedural interface and may well be more complete
  for your purposes.


pkgId: e3d67f610eda88508e14afeb605a478ba31ca722
name: local-perl-Task-Weaken
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Task-Weaken-1.04-1.src.rpm
checksum_type: sha
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: b70c3514b71d1d76c6565f3b1e46c6b2309a5f4b
name: local-perl-Template-Flute
arch: src
version: 0.0007
epoch: 0
release: 1
summary: Template-Flute - Modern designer-friendly HTML templating Engine
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Stefan Hornburg (Racke) <racke@linuxia.de>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Template-Flute-0.0007-1.src.rpm
checksum_type: sha
description:
  Template::Flute enables you to completely separate web design and programming
  tasks for dynamic web applications.

  Templates are designed to be designer-friendly; there's no inline code or mini
  templating language for your designers to learn - instead, standard HTML and CSS
  classes are used, leading to HTML that can easily be understood and edited by
  WYSIWYG editors and hand-coding designers alike.

  An example is easier than a wordy description:

  Given the following template snippet:

      <div class="customer_name">Mr A Test</div>
      <div class="customer_email">someone@example.com</div>

  and the following specification:

     <specification name="example" description="Example">
          <value name="customer_name" />
          <value name="email" field="customer_email" />
      </specification>

  Processing the above as follows:

      $flute = Template::Flute->new(
          template_file      => 'template.html',
          specification_file => 'spec.xml',
      );
      $flute->set_values({
          customer_name => 'Bob McTest',
          email => 'bob@example.com',
      });;
      print $flute->process;

  The resulting output would be:

      <div class="customer_name">Bob McTest</div>
      <div class="email">bob@example.com</div>


  In other words, rather than including a templating language within your
  templates which your designers must master and which could interfere with
  previews in WYSWYG tools, CSS selectors in the template are tied to your
  data structures or objects by a specification provided by the programmer.


pkgId: 61a53d95d2ef6e3a64efbf0ebe377c80391646c3
name: local-perl-Template-Flute
arch: src
version: 0.0081
epoch: 0
release: 1
summary: Template-Flute - Modern designer-friendly HTML templating Engine
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Stefan Hornburg (Racke) <racke@linuxia.de>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Template-Flute-0.0081-1.src.rpm
checksum_type: sha
description:
  Template::Flute enables you to completely separate web design and programming
  tasks for dynamic web applications.

  Templates are designed to be designer-friendly; there's no inline code or mini
  templating language for your designers to learn - instead, standard HTML and CSS
  classes are used, leading to HTML that can easily be understood and edited by
  WYSIWYG editors and hand-coding designers alike.

  An example is easier than a wordy description:

  Given the following template snippet:

      <div class="customer_name">Mr A Test</div>
      <div class="customer_email">someone@example.com</div>

  and the following specification:

     <specification name="example" description="Example">
          <value name="customer_name" />
          <value name="email" class="customer_email" />
      </specification>

  Processing the above as follows:

      $flute = Template::Flute->new(
          template_file      => 'template.html',
          specification_file => 'spec.xml',
      );
      $flute->set_values({
          customer_name => 'Bob McTest',
          email => 'bob@example.com',
      });;
      print $flute->process;

  The resulting output would be:

      <div class="customer_name">Bob McTest</div>
      <div class="email">bob@example.com</div>


  In other words, rather than including a templating language within your
  templates which your designers must master and which could interfere with
  previews in WYSWYG tools, CSS selectors in the template are tied to your
  data structures or objects by a specification provided by the programmer.


pkgId: 2d010696b26d12f1068729d1b8d49f33fce2fb18
name: local-perl-Template-Flute-PDF
arch: src
version: 0.0003
epoch: 0
release: 1
summary: Template-Flute-PDF - PDF generator for HTML templates
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Stefan Hornburg (Racke) <racke@linuxia.de>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Template-Flute-PDF-0.0003-1.src.rpm
checksum_type: sha
description:
  $flute = new Template::Flute (specification_file => 'invoice.xml',
                                template_file => 'invoice.html',
                                values => \%values);
    $flute->process();

    $pdf = new Template::Flute::PDF (template => $flute->template(),
                                    file => 'invoice.pdf');

    $pdf->process();


pkgId: a47e645f9cbc64fa8b247a629d906dfcb82c021f
name: local-perl-Template-Toolkit
arch: src
version: 2.20
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Template-Toolkit-2.20-1.src.rpm
checksum_type: sha
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: beaaabb87ea3b0eb275966440e8ed7aad1e7c937
name: local-perl-Term-Cap
arch: src
version: 1.12
epoch: 0
release: 1
summary: Term-Cap - Perl termcap interface
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jonathan Stowe <gellyfish@gellyfish.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Term-Cap-1.12-1.src.rpm
checksum_type: sha
description:
  These are low-level functions to extract and use capabilities from
  a terminal capability (termcap) database.

  More information on the terminal capabilities will be found in the
  termcap manpage on most Unix-like systems.


pkgId: 4942d4f92a886c517e0ee5e29b40e0ebffa7f146
name: local-perl-Term-Screen
arch: src
version: 1.03
epoch: 0
release: 1
summary: Term-Screen - A Simple all perl Term::Cap based screen positioning module
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: by Mark Kaehny <kaehny@execpc.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Term-Screen-1.03-1.src.rpm
checksum_type: sha
description:
  Term::Screen is a very simple screen positioning module that should
  work wherever C<Term::Cap> does. It is set up for Unix using stty's but
  these dependences are isolated by evals in the C<new> constructor. Thus
  you may create a child module implementing Screen with MS-DOS, ioctl,
  or other means to get raw and unblocked input. This is not a replacement
  for Curses -- it has no memory.  This was written so that it could be
  easily changed to fit nasty systems, and to be available first thing.

  The input functions getch, key_pressed, echo, and noecho are implemented
  so as to work under a fairly standard Unix system. They use 'stty'
  to set raw and no echo modes and turn on auto flush. All of these are
  'eval'ed so that this class can be inherited for new definitions easily.

  Term::Screen was designed to be "required", then used with object syntax
  as shown above. One quirk (which the author was used to so he didn't
  care) is that for function key translation, no delay is set. So for many
  terminals to get an esc character, you have to hit another char after it,
  generally another esc.


pkgId: 06b128eef7da221f6d9bddb9e0b596ed4dc0b973
name: local-perl-TermReadKey
arch: src
version: 2.30
epoch: 0
release: 6
summary: A perl module for simple terminal control
url: http://search.cpan.org/dist/TermReadKey/
rpm_license: Copyright only
rpm_group: Development/Libraries
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: local-perl-TermReadKey-2.30-6.src.rpm
checksum_type: sha
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: e480e78d03ad3829cb295c1878e740b85dc0e06d
name: local-perl-Test-Class
arch: src
version: 0.31
epoch: 0
release: 2.ep
summary: Easily create test classes in an xUnit/JUnit style
url: http://search.cpan.org/dist/Test-Class/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: local-perl-Test-Class-0.31-2.ep.src.rpm
checksum_type: sha
description:
  Test::Class provides a simple way of creating classes and objects to test
  your code in an xUnit style.


pkgId: 1ad0e46eb1c552b7aaa207b551dc88ddb9a25e27
name: local-perl-Test-File
arch: src
version: 1.25
epoch: 0
release: 1
summary: Test-File - Check file attributes
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: brian d foy <bdfoy@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-File-1.25-1.src.rpm
checksum_type: sha
description:
  This modules provides a collection of test utilities for file
  attributes.

  Some file attributes depend on the owner of the process testing the
  file in the same way the file test operators do.  For instance, root
  (or super-user or Administrator) may always be able to read files no
  matter the permissions.

  Some attributes don't make sense outside of Unix, either, so some
  tests automatically skip if they think they won't work on the
  platform.  If you have a way to make these functions work on Windows,
  for instance, please send me a patch. :)


pkgId: 3bc5327cd186e89bd574549026ce09e17af326f2
name: local-perl-Test-LongString
arch: src
version: 0.11
epoch: 0
release: 1
summary: Test-LongString - tests strings for equality, with more helpful failures
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Written by Rafael <>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-LongString-0.11-1.src.rpm
checksum_type: sha
description:
  This module provides some drop-in replacements for the string
  comparison functions of L<Test::More>, but which are more suitable
  when you test against long strings.  If you've ever had to search
  for text in a multi-line string like an HTML document, or find
  specific items in binary data, this is the module for you.


pkgId: d4fef68536e0ff5631e8cf7f9bc184cdc9eb832f
name: local-perl-Test-Manifest
arch: src
version: 1.22_03
epoch: 0
release: 1
summary: Test-Manifest - interact with a t/test_manifest file
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: brian d foy <bdfoy@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Manifest-1.22_03-1.src.rpm
checksum_type: sha
description:
  C<Test::Harness> assumes that you want to run all of the F<.t> files in the
  F<t/> directory in ascii-betical order during C<make test> unless you say
  otherwise.  This leads to some interesting naming schemes for test
  files to get them in the desired order. This interesting names ossify
  when they get into source control, and get even more interesting as
  more tests show up.

  C<Test::Manifest> overrides the default behaviour by replacing the
  test_via_harness target in the Makefile.  Instead of running at the
  F<t/*.t> files in ascii-betical order, it looks in the F<t/test_manifest>
  file to find out which tests you want to run and the order in which
  you want to run them.  It constructs the right value for MakeMaker to
  do the right thing.

  In F<t/test_manifest>, simply list the tests that you want to run.  Their
  order in the file is the order in which they run.  You can comment
  lines with a C<#>, just like in Perl, and C<Test::Manifest> will strip
  leading and trailing whitespace from each line.  It also checks that
  the specified file is actually in the F<t/> directory.  If the file does
  not exist, it does not put its name in the list of test files to run and
  it will issue a warning.

  Optionally, you can add a number after the test name in test_manifest
  to define sets of tests. See C<get_t_files> for more information.


pkgId: 25d539437e0ca39d4aa1565c223ad25eb2a5d56c
name: local-perl-Test-Memory-Cycle
arch: src
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Memory-Cycle-1.04-1.src.rpm
checksum_type: sha
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: 79669f7fc04d04cc24f1788861f2c2585602fb43
name: local-perl-Test-NoWarnings
arch: src
version: 0.084
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-NoWarnings-0.084-1.src.rpm
checksum_type: sha
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: 4aa04eb1884a2bc09b6ab045fe8c4d7e41d9bb6f
name: local-perl-Test-Output
arch: src
version: 0.10
epoch: 0
release: 1
summary: Test-Output - Utilities to test STDOUT and STDERR messages.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Shawn Sorichetti <ssoriche@coloredblocks.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Output-0.10-1.src.rpm
checksum_type: sha
description:
  Test::Output provides a simple interface for testing output sent to STDOUT
  or STDERR. A number of different utilies are included to try and be as
  flexible as possible to the tester.

  Originally this module was designed not to have external requirements,
  however, the features provided by L<Sub::Exporter> over what L<Exporter>
  provides is just to great to pass up.

  Test::Output ties STDOUT and STDERR using Test::Output::Tie.


pkgId: 2c074f50168c61017cfe42e024056a97dce634e1
name: local-perl-Test-Output
arch: src
version: 0.13
epoch: 0
release: 1
summary: Test-Output - Utilities to test STDOUT and STDERR messages.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: brian d foy <bdfoy@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Output-0.13-1.src.rpm
checksum_type: sha
description:
  Test::Output provides a simple interface for testing output sent to STDOUT
  or STDERR. A number of different utilities are included to try and be as
  flexible as possible to the tester.

  Originally this module was designed not to have external requirements,
  however, the features provided by L<Sub::Exporter> over what L<Exporter>
  provides is just to great to pass up.

  Test::Output ties STDOUT and STDERR using Test::Output::Tie.


pkgId: 712c1ec3873e64f46751ce9b990997bfbd2a2fa9
name: local-perl-Test-Pod
arch: src
version: 1.26
epoch: 0
release: 1
summary: Test-Pod - check for POD errors in files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Lester C <andy@petdance.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Pod-1.26-1.src.rpm
checksum_type: sha
description:
  Check POD files for errors or warnings in a test file, using
  C<Pod::Simple> to do the heavy lifting.


pkgId: 19e9f2d78cfd54e366561ca400db26dfea5a2fa3
name: local-perl-Test-Pod-Coverage
arch: src
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Pod-Coverage-1.08-1.src.rpm
checksum_type: sha
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: 7d017175c9f223c100f30da1779e405a3644c1e0
name: local-perl-Test-Requires
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Requires-0.06-1.src.rpm
checksum_type: sha
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: f82426fa4e504aed9011f8548b7500458e489a20
name: local-perl-Test-SharedFork
arch: src
version: 0.20
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-SharedFork-0.20-1.src.rpm
checksum_type: sha
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: b4746ae9b4c34f66dcef62565790941195bddb6b
name: local-perl-Test-Simple
arch: src
version: 0.94
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Simple-0.94-1.src.rpm
checksum_type: sha
description:
  ** If you are unfamiliar with testing B<read 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 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 );

  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.

  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: e45aaf4fb03ca4792950470bc1884aa2a73683b8
name: local-perl-Test-Strict
arch: src
version: 0.09
epoch: 0
release: 1
summary: Test-Strict - Check syntax, presence of use strict; and test coverage
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Pierre Denis C <pierre@itrelease.net>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Strict-0.09-1.src.rpm
checksum_type: sha
description:
  The most basic test one can write is "does it compile ?".
  This module tests if the code compiles and play nice with C<Test::Simple> modules.

  Another good practice this module can test is to "use strict;" in all perl files.

  By setting a minimum test coverage through C<all_cover_ok()>, a code author
  can ensure his code is tested above a preset level of I<kwality> throughout the development cycle.

  Along with L<Test::Pod>, this module can provide the first tests to setup for a module author.

  This module should be able to run under the -T flag for perl >= 5.6.
  All paths are untainted with the following pattern: C<qr|^([-+@\w./:\\]+)$|>
  controlled by C<$Test::Strict::UNTAINT_PATTERN>.


pkgId: acd9c1384e074dad6a2f45390c66c64bbb1cf3ea
name: local-perl-Test-Taint
arch: src
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Taint-1.04-1.src.rpm
checksum_type: sha
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: 7630d667e35d852c0afcf1c35725610cdbc3f281
name: local-perl-Test-Tester
arch: src
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Tester-0.107-1.src.rpm
checksum_type: sha
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: 10cf1dc2a9d55fb80a9a872f32a8f12cee5bc5db
name: local-perl-Test-WWW-Mechanize
arch: src
version: 1.20
epoch: 0
release: 1
summary: Test-WWW-Mechanize - Testing-specific WWW::Mechanize subclass
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Lester <andy@petdance.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-WWW-Mechanize-1.20-1.src.rpm
checksum_type: sha
description:
  Test::WWW::Mechanize is a subclass of L<WWW::Mechanize> that incorporates
  features for web application testing.  For example:

      use Test::More tests => 5;
      use Test::WWW::Mechanize;

      my $mech = Test::WWW::Mechanize->new;
      $mech->get_ok( $page );
      $mech->base_is( 'http://petdance.com/', 'Proper <BASE HREF>' );
      $mech->title_is( "Invoice Status", "Make sure we're on the invoice page" );
      $mech->content_contains( "Andy Lester", "My name somewhere" );
      $mech->content_like( qr/(cpan|perl)\.org/, "Link to perl.org or CPAN" );

  This is equivalent to:

      use Test::More tests => 5;
      use WWW::Mechanize;

      my $mech = WWW::Mechanize->new;
      $mech->get( $page );
      ok( $mech->success );
      is( $mech->base, 'http://petdance.com', 'Proper <BASE HREF>' );
      is( $mech->title, "Invoice Status", "Make sure we're on the invoice page" );
      ok( index( $mech->content, "Andy Lester" ) >= 0, "My name somewhere" );
      like( $mech->content, qr/(cpan|perl)\.org/, "Link to perl.org or CPAN" );

  but has nicer diagnostics if they fail.

  Default descriptions will be supplied for most methods if you omit them. e.g.

      my $mech = Test::WWW::Mechanize->new;
      $mech->get_ok( 'http://petdance.com/' );
      $mech->base_is( 'http://petdance.com/' );
      $mech->title_is( "Invoice Status" );
      $mech->content_contains( "Andy Lester" );
      $mech->content_like( qr/(cpan|perl)\.org/ );

  results in

      ok - Got 'http://petdance.com/' ok
      ok - Base is 'http://petdance.com/'
      ok - Title is 'Invoice Status'
      ok - Content contains 'Andy Lester'
      ok - Content is like '(?-xism:(cpan|perl)\.org)'


pkgId: 7078832c5b0a386422fec6814682971b5a26bfa4
name: local-perl-Test-Warn
arch: src
version: 0.11
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Test-Warn-0.11-1.src.rpm
checksum_type: sha
description:
  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: d7001ed0cc2c1bbdcf0c89e81f24d810ef36a10f
name: local-perl-Text-CSV
arch: src
version: 1.10
epoch: 0
release: 1
summary: Text-CSV - comma-separated values manipulator (using XS or PurePerl)
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-CSV-1.10-1.src.rpm
checksum_type: sha
description:
  Text::CSV provides facilities for the composition and decomposition of
  comma-separated values using L<Text::CSV_XS> or its pure Perl version.

  An instance of the Text::CSV class can combine fields into a CSV string
  and parse a CSV string into fields.

  The module accepts either strings or files as input and can utilize any
  user-specified characters as delimiters, separators, and escapes so it is
  perhaps better called ASV (anything separated values) rather than just CSV.


pkgId: feae0eb954041b41e8965f2b2cf36b1a18da8272
name: local-perl-Text-CSV-Simple
arch: src
version: 1.00
epoch: 0
release: 1
summary: Text-CSV-Simple - Simpler parsing of CSV files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Tony Bowden <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-CSV-Simple-1.00-1.src.rpm
checksum_type: sha
description:
  Parsing CSV files is nasty. It seems so simple, but it usually isn't.
  Thankfully Text::CSV_XS takes care of most of that nastiness for us.

  Like many modules which have to deal with all manner of nastiness and
  edge cases, however, it can be clumsy to work with in the simple case.

  Thus this module.

  We simply provide a little wrapper around Text::CSV_XS to streamline the
  common case scenario. (Or at least B<my> common case scenario; feel free
  to write your own wrapper if this one doesn't do what you want).


pkgId: a2a04fdf0a7bb61d3ce7f6851ab9e2e075c91366
name: local-perl-Text-CSV_XS
arch: src
version: 0.52
epoch: 0
release: 1
summary: Text-CSV_XS - Comma-Separated Values manipulation routines
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: H.Merijn Brand <h.merijn@xs4all.nl>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-CSV_XS-0.52-1.src.rpm
checksum_type: sha
description:
  Text::CSV_XS provides facilities for the composition and decomposition of
  comma-separated values.  An instance of the Text::CSV_XS class can combine
  fields into a CSV string and parse a CSV string into fields.

  The module accepts either strings or files as input and can utilize any
  user-specified characters as delimiters, separators, and escapes so it is
  perhaps better called ASV (anything separated values) rather than just CSV.


pkgId: edd7f053da7971fb563e76460e60e72b37df97bb
name: local-perl-Text-Capitalize
arch: src
version: 0.5
epoch: 0
release: 1
summary: Text-Capitalize - capitalize strings ("to WORK AS titles" becomes "To Work as Titles")
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Joseph Brenner <doom@kzsu.stanford.edu>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-Capitalize-0.5-1.src.rpm
checksum_type: sha
description:
  Text::Capitalize provides a few different flavors of procedures
  for B<title-like> formatting for strings.

  For the "capitalize" function B<Title-like> (written by
  Stanislaw Y. Pusep) formatting consists of ensuring that the
  first letter of each word is uppercase, and that the rest is
  lowercase.

  The "capitalize_title" function tries to get closer to
  English title capitalization rules (discussed below) where
  only the "important" words are supposed to be capitalized.
  There are also some customization features provided to allow
  the user to choose variant rules.

  Examples of title formatting with "capitalize":

  =over

  =item 'lost watches of splitsville' becomes 'Lost Watches Of Splitsville'

  =item 'KiLLiNG TiMe' becomes 'Killing Time'

  =back

  Some simple examples of title formatting with "capitalize_title":

  =over

  =item 'we have come to wound the autumnal city' becomes 'We Have Come to Wound the Autumnal City'

  =item 'ask for whom they ask for' becomes 'Ask for Whom They Ask For'

  =back

  Text::Capitalize also provides some functions for special effects
  such as "scramble_case", which typically would be used for this sort
  of transformation:

  =over

  =item 'get whacky' might become 'gET wHaCkY'

  =back


pkgId: 7a4567bfb4f1a0b5cc0c10328d4b2b494d1c9465
name: local-perl-Text-Diff
arch: src
version: 0.35
epoch: 0
release: 1
summary: Text-Diff - Perform diffs on files and record sets
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Barrie Slaymaker <barries@slaysys.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-Diff-0.35-1.src.rpm
checksum_type: sha
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.


pkgId: f3c6fb20563ee09351c2a6dd734350cb31cd286a
name: local-perl-Text-PDF
arch: src
version: 0.29
epoch: 0
release: 1
summary: Text-PDF - PDF Manipulation and generation
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: martin_hosken@sil.org
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-PDF-0.29-1.src.rpm
checksum_type: sha
description:
  This module allows interaction with existing PDF files directly. It includes
  various tools including:

    pdfbklt - make booklets out of existing PDF files
    pdfrevert - remove edits from a PDF file
    pdfstamp - stamp text on each page of a PDF file

  various example programs are also included


pkgId: 3a24b91f35aa14f9f3fe8861df173a3821a90e26
name: local-perl-Text-Query
arch: src
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: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-Query-0.07-1.src.rpm
checksum_type: sha
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: a2fdc7503c9c059cf5957bb6c6bd368b43dd73fe
name: local-perl-Text-ScriptTemplate
arch: src
version: 0.08
epoch: 0
release: 1
summary: Text-ScriptTemplate - Standalone ASP/JSP/PHP-style template processor
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Taisuke Yamada <tyamadajp@spam.rakugaki.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-ScriptTemplate-0.08-1.src.rpm
checksum_type: sha
description:
  This is a successor of Text::SimpleTemplate, a module for template-
  based text generation.

  Template-based text generation is a way to separate program code and
  data, so non-programmer can control final result (like HTML) as desired
  without tweaking the program code itself. By doing so, jobs like website
  maintenance is much easier because you can leave program code unchanged
  even if page redesign was needed.

  The idea of this module is simple. Whenever a block of text surrounded
  by '<%' and '%>' (or any pair of delimiters you specify) is found, it
  will be taken as Perl expression, and will be handled specially by
  template processing engine. With this module, Perl script and text
  can be intermixed closely.

  Major goal of this library is to provide support of powerful PHP-style
  template with smaller resource. This is useful when PHP, Java/JSP,
  or Apache::ASP is overkill, but their template style is still desired.


pkgId: f96a94e481769d8cbd3ea7b8c23a0c40f4865c39
name: local-perl-Text-Striphigh
arch: src
version: 0.02
epoch: 0
release: 1
summary: Text-Striphigh - Perl extension to strip the high bit off of ISO-8859-1 text.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: jpc@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-Striphigh-0.02-1.src.rpm
checksum_type: sha
description:
  The Text::Striphigh module exports a single function: C<striphigh>. This
  function takes one argument, a string possibly containing high ASCII
  characters in the ISO-8859-1 character set, and transforms this into a
  string containing only 7 bits ASCII characters, by substituting every
  high bit character with a similar looking standard ASCII character, or
  with a sequence of standard ASCII characters.

  Because of precisely the deficiency this package tries to offer a workaround
  for is present in some of the things that process pod, there are no
  examples in this manpage. Look at the source or the test script if you
  want examples.


pkgId: 2363ee8ed55b560bc932e51e354a8314f162bfed
name: local-perl-Text-Template
arch: src
version: 1.45
epoch: 0
release: 1
summary: Text-Template - Expand template text with embedded Perl
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: this software to <Cmjd-perl-template+@plover.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-Template-1.45-1.src.rpm
checksum_type: sha
description:
  This is a library for generating form letters, building HTML pages, or
  filling in templates generally.  A `template' is a piece of text that
  has little Perl programs embedded in it here and there.  When you
  `fill in' a template, you evaluate the little programs and replace
  them with their values.

  You can store a template in a file outside your program.  People can
  modify the template without modifying the program.  You can separate
  the formatting details from the main code, and put the formatting
  parts of the program into the template.  That prevents code bloat and
  encourages functional separation.


pkgId: 8c784e24e01bf1810e10daa6626761598e40d42d
name: local-perl-Text-Unaccent
arch: src
version: 1.08
epoch: 0
release: 2
summary: Text-Unaccent - Remove accents from a string
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Loic Dachary <loic@senga.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Text-Unaccent-1.08-2.src.rpm
checksum_type: sha
description:
  Text::Unaccent is a module that remove accents from a string.
  C<unac_string> converts the input string from the
  specified  charset to UTF-16 and call
  C<unac_string_utf16> to
  return the unaccented equivalent. The conversion from  and
  to  UTF-16  is  done  with iconv(1).


pkgId: 8ddc749b9073279319696e9357707a5856ee3f39
name: local-perl-Tie-IxHash
arch: src
version: 1.21
epoch: 0
release: 1
summary: Tie-IxHash - ordered associative arrays for Perl
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Gurusamy Sarathy <gsar@umich.edu>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Tie-IxHash-1.21-1.src.rpm
checksum_type: sha
description:
  This Perl module implements Perl hashes that preserve the order in which the
  hash elements were added.  The order is not affected when values
  corresponding to existing keys in the IxHash are changed.  The elements can
  also be set to any arbitrary supplied order.  The familiar perl array
  operations can also be performed on the IxHash.


pkgId: 11c8c9f009ef8cdc0aef7f40677ce9c61f798f9b
name: local-perl-Tie-Restore
arch: src
version: 0.11
epoch: 0
release: 1
summary: Tie-Restore - restores ties to an existing object
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Robby Walker <webmaster@pointwriter.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Tie-Restore-0.11-1.src.rpm
checksum_type: sha
description:
  Provides the opposite of the 'tied' function.  Say you have %hash that
  is tied to $object.  Then, it is relatively simple to get $object from
  %hash simply by saying

   $object = tied %hash;

  But, how does one go the other way?  Simple, with Tie::Restore

   tie %hash, 'Tie::Restore', $object;

  Works for any kind of tie. (scalar, array, hash, filehandle)


pkgId: 142ff1ff923e506de5981a67d134d82d854d6e2b
name: local-perl-Tie-StrictHash
arch: src
version: 1.0
epoch: 0
release: 1
summary: Tie-StrictHash - A hash with 'strict'-like semantics
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Kevin Michael Vail <kevin@vaildc.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Tie-StrictHash-1.0-1.src.rpm
checksum_type: sha
description:
  C<Tie::StrictHash> is a module for implementing some of the same semantics for
  hash members that 'use strict' gives to variables.  The following constraints
  are applied to a strict hash:

  =over 4

  =item o

  No new keys may be added to the hash except through the B<add> method of the
  hash control object.

  =item o

  No keys may be deleted except through the B<delete> method of the hash control
  object.

  =item o

  The hash cannot be re-initialized (cleared) except through the B<clear> method
  of the hash control object.

  =item o

  Attempting to retrieve the value for a key that doesn't exist is a fatal error.

  =item o

  Attempting to store a value for a key that doesn't exist is a fatal error.

  =back

  In order to make any changes or modifications to the hash, you must either keep
  the return value from B<strict_hash> (or B<tie>) or retrieve it by using C<tied
  I<%hash>>. Think of it as the "key" that "unlocks" the hash so that you can make
  changes to it.

  The original reason for writing this module was for classes that implement
  an object as a hash, using hash members as instance variables.  It's all too
  easy to use the wrong member name, with the same results as misspelling a
  variable name when C<use strict> isn't in effect.

  Note that just as C<use strict> allows you to create new variables by either
  specifying an explicit package name or by using C<use vars>, a strict hash
  allows you to create or delete members by using the appropriate methods.
  However, it does prevent you from creating or deleting members accidentally.
  This is in keeping with the general philosophy of Perl.

  If you import the pseudo-symbol C<warn>, Tie::StrictHash will only issue
  warning messages rather than dying when an attempt is made to reference a hash
  value that doesn't exist.

  If you import the pseudo-symbol C<confess>, either by itself or along with
  C<warn>, you'll get a stack backtrace as well when something happens.


pkgId: 38d3e9eef1cf858774832ffb0aa39d1dfb681f7b
name: local-perl-Tie-Sub
arch: src
version: 1.001
epoch: 0
release: 1
summary: Tie-Sub - Tying a subroutine, function or method to a hash
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Steffen Winkler <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Tie-Sub-1.001-1.src.rpm
checksum_type: sha
description:
  Subroutines don't have interpreted into strings.
  The module ties a subroutine to a hash.
  The subroutine is executed at fetch hash.
  At long last this is the same, only the notation is shorter.

  Alternative to

      " ... ${\ subroutine('abc') } ... "
      
      " ... @{[ subroutine('abc') ]} ... "
      
      '...' . subroutine('abc') . '...'

  write

      " ... $subroutine{abc} ... "


  Sometimes the subroutine expects more than 1 parameter.
  Then submit a reference on an array as 'hash key'.
  The tied subroutine will get the parameters always as list.

  Use any reference to give back more then 1 return value.
  The caller get back this reference.
  There is no way to return a list.


pkgId: 714fad0eb23ac426cff2f0956bafd0b1b3bed84f
name: local-perl-Tie-ToObject
arch: src
version: 0.03
epoch: 0
release: 1
summary: Tie-ToObject - Tie to an existing object.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Yuval Kogman <Eltnothingmuch@woobling.orgEgt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Tie-ToObject-0.03-1.src.rpm
checksum_type: sha
description:
  While L<perldoc/tie> allows tying to an arbitrary object, the class in question
  must support this in it's implementation of C<TIEHASH>, C<TIEARRAY> or
  whatever.

  This class provides a very tie constructor that simply returns the object it
  was given as it's first argument.

  This way side effects of calling C<< $object->TIEHASH >> are avoided.

  This is used in L<Data::Visitor> in order to tie a variable to an already
  existing object. This is also useful for cloning, when you want to clone the
  internal state object instead of going through the tie interface for that
  variable.


pkgId: c09ef7c5b12ba81c3e0c34ba15ad8228d37c8bfd
name: local-perl-Tie-Watch
arch: src
version: 1.2
epoch: 0
release: 1
summary: Tie-Watch - Place watchpoints on Perl (and Tk) variables
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Steve Lidie (Stephen.O.Lidie@Lehigh.EDU)
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Tie-Watch-1.2-1.src.rpm
checksum_type: sha
description:
  This class module binds one or more subroutines of your devising to a
  Perl variable.  All variables can have B<FETCH>, B<STORE> and
  B<DESTROY> callbacks.  Additionally, arrays can define B<CLEAR>,
  B<DELETE>, B<EXISTS>, B<EXTEND>, B<FETCHSIZE>, B<POP>, B<PUSH>,
  B<SHIFT>, B<SPLICE>, B<STORESIZE> and B<UNSHIFT> callbacks, and hashes
  can define B<CLEAR>, B<DELETE>, B<EXISTS>, B<FIRSTKEY> and B<NEXTKEY>
  callbacks.  If these term are unfamiliar to you, I I<really> suggest
  you read L<perltie>.

  With Tie::Watch you can:

   . alter a variable's value
   . prevent a variable's value from being changed
   . invoke a Perl/Tk callback when a variable changes
   . trace references to a variable

  Callback format is patterned after the Perl/Tk scheme: supply either a
  code reference, or, supply an array reference and pass the callback
  code reference in the first element of the array, followed by callback
  arguments.  (See examples in the Synopsis, above.)

  Tie::Watch provides default callbacks for any that you fail to
  specify.  Other than negatively impacting performance, they perform
  the standard action that you'd expect, so the variable behaves
  "normally".  Once you override a default callback, perhaps to insert
  debug code like print statements, your callback normally finishes by
  calling the underlying (overridden) method.  But you don't have to!

  To map a tied method name to a default callback name simply lowercase
  the tied method name and uppercase its first character.  So FETCH
  becomes Fetch, NEXTKEY becomes Nextkey, etcetera.

  Here are two callbacks for a scalar. The B<FETCH> (read) callback does
  nothing other than illustrate the fact that it returns the value to
  assign the variable.  The B<STORE> (write) callback uppercases the
  variable and returns it.  In all cases the callback I<must> return the
  correct read or write value - typically, it does this by invoking the
  underlying method.

   my $fetch_scalar = sub {
       my($self) = @_;
       $self->Fetch;
   };

   my $store_scalar = sub {
       my($self, $new_val) = @_;
       $self->Store(uc $new_val);
   };

  Here are B<FETCH> and B<STORE> callbacks for either an array or hash.
  They do essentially the same thing as the scalar callbacks, but
  provide a little more information.

   my $fetch = sub {
       my($self, $key) = @_;
       my $val = $self->Fetch($key);
       print "In fetch callback, key=$key, val=", $self->Say($val);
       my $args = $self->Args(-fetch);
       print ", args=('", join("', '",  @$args), "')" if $args;
       print ".\n";
       $val;
   };

   my $store = sub {
       my($self, $key, $new_val) = @_;
       my $val = $self->Fetch($key);
       $new_val = uc $new_val;
       $self->Store($key, $new_val);
       print "In store callback, key=$key, val=", $self->Say($val),
         ", new_val=", $self->Say($new_val);
       my $args = $self->Args(-store);
       print ", args=('", join("', '",  @$args), "')" if $args;
       print ".\n";
       $new_val;
   };

  In all cases, the first parameter is a reference to the Watch object,
  used to invoke the following class methods.


pkgId: 5c44bf97c0ef7b3daf7fa0a2a10027ee8d0b9bac
name: local-perl-Time-Clock
arch: src
version: 0.12
epoch: 0
release: 1
summary: Time-Clock - Twenty-four hour clock object with nanosecond precision.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: John C Siracusa <siracusa@gmail.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Time-Clock-0.12-1.src.rpm
checksum_type: sha
description:
  A L<Time::Clock> object is a twenty-four hour clock with nanosecond precision and wrap-around.  It is a clock only; it has absolutely no concept of dates.  Vagaries of date/time such as leap seconds and daylight savings time are unsupported.

  When a L<Time::Clock> object hits 23:59:59.999999999 and at least one more nanosecond is added, it will wrap around to 00:00:00.000000000.  This works in reverse when time is subtracted.

  L<Time::Clock> objects automatically stringify to a user-definable format.


pkgId: e928a681b8ef5b8754bd3228e810f0283aad6449
name: local-perl-Time-HiRes
arch: src
version: 1.9715
epoch: 0
release: 1
summary: Time-HiRes - High resolution alarm, sleep, gettimeofday, interval timers
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Jarkko Hietaniemi <jhi@iki.fi>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Time-HiRes-1.9715-1.src.rpm
checksum_type: sha
description:
  The "Time::HiRes" module implements a Perl interface to the
  "usleep", "nanosleep", "ualarm", "gettimeofday", and
  "setitimer"/"getitimer" system calls, in other words, high
  resolution time and timers. See the "EXAMPLES" section below and the
  test scripts for usage; see your system documentation for the
  description of the underlying "nanosleep" or "usleep", "ualarm",
  "gettimeofday", and "setitimer"/"getitimer" calls.

  If your system lacks "gettimeofday()" or an emulation of it you don't
  get "gettimeofday()" or the one-argument form of "tv_interval()".
  If your system lacks all of "nanosleep()", "usleep()",
  "select()", and "poll", you don't get "Time::HiRes::usleep()",
  "Time::HiRes::nanosleep()", or "Time::HiRes::sleep()".
  If your system lacks both "ualarm()" and "setitimer()" you don't get
  "Time::HiRes::ualarm()" or "Time::HiRes::alarm()".

  If you try to import an unimplemented function in the "use" statement
  it will fail at compile time.

  If your subsecond sleeping is implemented with "nanosleep()" instead
  of "usleep()", you can mix subsecond sleeping with signals since
  "nanosleep()" does not use signals.  This, however, is not portable,
  and you should first check for the truth value of
  &Time::HiRes::d_nanosleep to see whether you have nanosleep, and
  then carefully read your "nanosleep()" C API documentation for any
  peculiarities.

  If you are using "nanosleep" for something else than mixing sleeping
  with signals, give some thought to whether Perl is the tool you should
  be using for work requiring nanosecond accuracies.

  Remember that unless you are working on a *hard realtime* system,
  any clocks and timers will be imprecise, especially so if you are working
  in a pre-emptive multiuser system.  Understand the difference between
  *wallclock time* and process time (in UNIX-like systems the sum of
  *user* and *system* times).  Any attempt to sleep for X seconds will
  most probably end up sleeping more than that, but don't be surpised
  if you end up sleeping slightly less.

  The following functions can be imported from this module.
  No functions are exported by default.

  =over 4

  =item gettimeofday ()

  In array context returns a two-element array with the seconds and
  microseconds since the epoch.  In scalar context returns floating
  seconds like "Time::HiRes::time()" (see below).

  =item usleep ( $useconds )

  Sleeps for the number of microseconds (millionths of a second)
  specified.  Returns the number of microseconds actually slept.
  Can sleep for more than one second, unlike the "usleep" system call.
  Can also sleep for zero seconds, which often works like a *thread yield*.
  See also "Time::HiRes::usleep()", "Time::HiRes::sleep()", and
  "Time::HiRes::clock_nanosleep()".

  Do not expect usleep() to be exact down to one microsecond.

  =item nanosleep ( $nanoseconds )

  Sleeps for the number of nanoseconds (1e9ths of a second) specified.
  Returns the number of nanoseconds actually slept (accurate only to
  microseconds, the nearest thousand of them).  Can sleep for more than
  one second.  Can also sleep for zero seconds, which often works like
  a *thread yield*.  See also "Time::HiRes::sleep()",
  "Time::HiRes::usleep()", and "Time::HiRes::clock_nanosleep()".

  Do not expect nanosleep() to be exact down to one nanosecond.
  Getting even accuracy of one thousand nanoseconds is good.

  =item ualarm ( $useconds [, $interval_useconds ] )

  Issues a "ualarm" call; the $interval_useconds is optional and
  will be zero if unspecified, resulting in "alarm"-like behaviour.

  Returns the remaining time in the alarm in microseconds, or "undef"
  if an error occurred.

  ualarm(0) will cancel an outstanding ualarm().

  Note that the interaction between alarms and sleeps is unspecified.

  =item tv_interval

  tv_interval ( $ref_to_gettimeofday [, $ref_to_later_gettimeofday] )

  Returns the floating seconds between the two times, which should have
  been returned by "gettimeofday()". If the second argument is omitted,
  then the current time is used.

  =item time ()

  Returns a floating seconds since the epoch. This function can be
  imported, resulting in a nice drop-in replacement for the "time"
  provided with core Perl; see the "EXAMPLES" below.

  NOTE 1: This higher resolution timer can return values either less
  or more than the core "time()", depending on whether your platform
  rounds the higher resolution timer values up, down, or to the nearest second
  to get the core "time()", but naturally the difference should be never
  more than half a second.  See also "clock_getres", if available
  in your system.

  NOTE 2: Since Sunday, September 9th, 2001 at 01:46:40 AM GMT, when
  the "time()" seconds since epoch rolled over to 1_000_000_000, the
  default floating point format of Perl and the seconds since epoch have
  conspired to produce an apparent bug: if you print the value of
  "Time::HiRes::time()" you seem to be getting only five decimals, not
  six as promised (microseconds).  Not to worry, the microseconds are
  there (assuming your platform supports such granularity in the first
  place).  What is going on is that the default floating point format of
  Perl only outputs 15 digits.  In this case that means ten digits
  before the decimal separator and five after.  To see the microseconds
  you can use either "printf"/"sprintf" with "%.6f", or the
  "gettimeofday()" function in list context, which will give you the
  seconds and microseconds as two separate values.

  =item sleep ( $floating_seconds )

  Sleeps for the specified amount of seconds.  Returns the number of
  seconds actually slept (a floating point value).  This function can
  be imported, resulting in a nice drop-in replacement for the "sleep"
  provided with perl, see the "EXAMPLES" below.

  Note that the interaction between alarms and sleeps is unspecified.

  =item alarm ( $floating_seconds [, $interval_floating_seconds ] )

  The "SIGALRM" signal is sent after the specified number of seconds.
  Implemented using "setitimer()" if available, "ualarm()" if not.
  The $interval_floating_seconds argument is optional and will be
  zero if unspecified, resulting in "alarm()"-like behaviour.  This
  function can be imported, resulting in a nice drop-in replacement for
  the "alarm" provided with perl, see the "EXAMPLES" below.

  Returns the remaining time in the alarm in seconds, or "undef"
  if an error occurred.

  NOTE 1: With some combinations of operating systems and Perl
  releases "SIGALRM" restarts "select()", instead of interrupting it.
  This means that an "alarm()" followed by a "select()" may together
  take the sum of the times specified for the the "alarm()" and the
  "select()", not just the time of the "alarm()".

  Note that the interaction between alarms and sleeps is unspecified.

  =item setitimer ( $which, $floating_seconds [, $interval_floating_seconds ] )

  Start up an interval timer: after a certain time, a signal ($which) arrives,
  and more signals may keep arriving at certain intervals.  To disable
  an "itimer", use $floating_seconds of zero.  If the
  $interval_floating_seconds is set to zero (or unspecified), the
  timer is disabled after the next delivered signal.

  Use of interval timers may interfere with "alarm()", "sleep()",
  and "usleep()".  In standard-speak the "interaction is unspecified",
  which means that *anything* may happen: it may work, it may not.

  In scalar context, the remaining time in the timer is returned.

  In list context, both the remaining time and the interval are returned.

  There are usually three or four interval timers (signals) available: the
  $which can be "ITIMER_REAL", "ITIMER_VIRTUAL", "ITIMER_PROF", or
  "ITIMER_REALPROF".  Note that which ones are available depends: true
  UNIX platforms usually have the first three, but (for example) Win32
  and Cygwin have only "ITIMER_REAL", and only Solaris seems to have
  "ITIMER_REALPROF" (which is used to profile multithreaded programs).

  "ITIMER_REAL" results in "alarm()"-like behaviour.  Time is counted in
  *real time*; that is, wallclock time.  "SIGALRM" is delivered when
  the timer expires.

  "ITIMER_VIRTUAL" counts time in (process) *virtual time*; that is,
  only when the process is running.  In multiprocessor/user/CPU systems
  this may be more or less than real or wallclock time.  (This time is
  also known as the *user time*.)  "SIGVTALRM" is delivered when the
  timer expires.

  "ITIMER_PROF" counts time when either the process virtual time or when
  the operating system is running on behalf of the process (such as I/O).
  (This time is also known as the *system time*.)  (The sum of user
  time and system time is known as the *CPU time*.)  "SIGPROF" is
  delivered when the timer expires.  "SIGPROF" can interrupt system calls.

  The semantics of interval timers for multithreaded programs are
  system-specific, and some systems may support additional interval
  timers.  For example, it is unspecified which thread gets the signals.
  See your "setitimer()" documentation.

  =item getitimer ( $which )

  Return the remaining time in the interval timer specified by $which.

  In scalar context, the remaining time is returned.

  In list context, both the remaining time and the interval are returned.
  The interval is always what you put in using "setitimer()".

  =item clock_gettime ( $which )

  Return as seconds the current value of the POSIX high resolution timer
  specified by $which.  All implementations that support POSIX high
  resolution timers are supposed to support at least the $which value
  of "CLOCK_REALTIME", which is supposed to return results close to the
  results of "gettimeofday", or the number of seconds since 00:00:00:00
  January 1, 1970 Greenwich Mean Time (GMT).  Do not assume that
  CLOCK_REALTIME is zero, it might be one, or something else.
  Another potentially useful (but not available everywhere) value is
  "CLOCK_MONOTONIC", which guarantees a monotonically increasing time
  value (unlike time(), which can be adjusted).  See your system
  documentation for other possibly supported values.

  =item clock_getres ( $which )

  Return as seconds the resolution of the POSIX high resolution timer
  specified by $which.  All implementations that support POSIX high
  resolution timers are supposed to support at least the $which value
  of "CLOCK_REALTIME", see "clock_gettime".

  =item clock_nanosleep ( $which, $nanoseconds, $flags = 0)

  Sleeps for the number of nanoseconds (1e9ths of a second) specified.
  Returns the number of nanoseconds actually slept.  The $which is the
  "clock id", as with clock_gettime() and clock_getres().  The flags
  default to zero but "TIMER_ABSTIME" can specified (must be exported
  explicitly) which means that $nanoseconds is not a time interval
  (as is the default) but instead an absolute time.  Can sleep for more
  than one second.  Can also sleep for zero seconds, which often works
  like a *thread yield*.  See also "Time::HiRes::sleep()",
  "Time::HiRes::usleep()", and "Time::HiRes::nanosleep()".

  Do not expect clock_nanosleep() to be exact down to one nanosecond.
  Getting even accuracy of one thousand nanoseconds is good.

  =item clock()

  Return as seconds the *process time* (user + system time) spent by
  the process since the first call to clock() (the definition is not
  "since the start of the process", though if you are lucky these times
  may be quite close to each other, depending on the system).  What this
  means is that you probably need to store the result of your first call
  to clock(), and subtract that value from the following results of clock().

  The time returned also includes the process times of the terminated
  child processes for which wait() has been executed.  This value is
  somewhat like the second value returned by the times() of core Perl,
  but not necessarily identical.  Note that due to backward
  compatibility limitations the returned value may wrap around at about
  2147 seconds or at about 36 minutes.

  =item stat

  =item stat FH

  =item stat EXPR

  As "stat" in perlfunc but with the access/modify/change file timestamps
  in subsecond resolution, if the operating system and the filesystem
  both support such timestamps.  To override the standard stat():

      use Time::HiRes qw(stat);

  Test for the value of &Time::HiRes::d_hires_stat to find out whether
  the operating system supports subsecond file timestamps: a value
  larger than zero means yes. There are unfortunately no easy
  ways to find out whether the filesystem supports such timestamps.
  UNIX filesystems often do; NTFS does; FAT doesn't (FAT timestamp
  granularity is two seconds).

  A zero return value of &Time::HiRes::d_hires_stat means that
  Time::HiRes::stat is a no-op passthrough for CORE::stat(),
  and therefore the timestamps will stay integers.  The same
  thing will happen if the filesystem does not do subsecond timestamps,
  even if the &Time::HiRes::d_hires_stat is non-zero.

  In any case do not expect nanosecond resolution, or even a microsecond
  resolution.  Also note that the modify/access timestamps might have
  different resolutions, and that they need not be synchronized, e.g.
  if the operations are

      write
      stat # t1
      read
      stat # t2

  the access time stamp from t2 need not be greater-than the modify
  time stamp from t1: it may be equal or *less*.

  =back


pkgId: 06b1943f085d39767d8c9eb1b58ebab1b6ec7829
name: local-perl-Time-modules
arch: src
version: 2006.0814
epoch: 0
release: 1
summary: Time-modules - Parse and format time values
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: David Muir Sharnoff <muir@idiom.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Time-modules-2006.0814-1.src.rpm
checksum_type: sha
description:
  This module recognizes the above date/time formats.   Usually a
  date and a time are specified.  There are numerous options for
  controlling what is recognized and what is not.

  The return code is always the time in seconds since January 1st, 1970
  or undef if it was unable to parse the time.

  If a timezone is specified it must be after the time.  Year specifications
  can be tacked onto the end of absolute times.

  If C<parsedate()> is called from array context, then it will return two
  elements.  On sucessful parses, it will return the seconds and what
  remains of its input string.  On unsucessful parses, it will return
  C<undef> and an error string.


pkgId: 0a956f8dcaae48f8a56ac74b0126f410a7d28915
name: local-perl-Tree-DAG_Node
arch: src
version: 1.06
epoch: 0
release: 1
summary: Tree-DAG_Node - (super)class for representing nodes in a tree
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: David Hand, <cogent@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Tree-DAG_Node-1.06-1.src.rpm
checksum_type: sha
description:
  This class encapsulates/makes/manipulates objects that represent nodes
  in a tree structure. The tree structure is not an object itself, but
  is emergent from the linkages you create between nodes.  This class
  provides the methods for making linkages that can be used to build up
  a tree, while preventing you from ever making any kinds of linkages
  which are not allowed in a tree (such as having a node be its own
  mother or ancestor, or having a node have two mothers).

  This is what I mean by a "tree structure", a bit redundantly stated:

  * A tree is a special case of an acyclic directed graph.

  * A tree is a network of nodes where there's exactly one root
  node (i.e., 'the top'), and the only primary relationship between nodes
  is the mother-daugher relationship.

  * No node can be its own mother, or its mother's mother, etc.

  * Each node in the tree has exactly one "parent" (node in the "up"
  direction) -- except the root, which is parentless.

  * Each node can have any number (0 to any finite number) of daughter
  nodes.  A given node's daughter nodes constitute an I<ordered> list.
  (However, you are free to consider this ordering irrelevant.
  Some applications do need daughters to be ordered, so I chose to
  consider this the general case.)

  * A node can appear in only one tree, and only once in that tree.
  Notably (notable because it doesn't follow from the two above points),
  a node cannot appear twice in its mother's daughter list.

  * In other words, there's an idea of up (toward the root) versus
  down (away from the root), and left (i.e., toward the start (index 0)
  of a given node's daughter list) versus right (toward the end of a
  given node's daughter list).

  Trees as described above have various applications, among them:
  representing syntactic constituency, in formal linguistics;
  representing contingencies in a game tree; representing abstract
  syntax in the parsing of any computer language -- whether in
  expression trees for programming languages, or constituency in the
  parse of a markup language document.  (Some of these might not use the
  fact that daughters are ordered.)

  (Note: B-Trees are a very special case of the above kinds of trees,
  and are best treated with their own class.  Check CPAN for modules
  encapsulating B-Trees; or if you actually want a database, and for
  some reason ended up looking here, go look at L<AnyDBM_File>.)

  Many base classes are not usable except as such -- but Tree::DAG_Node
  can be used as a normal class.  You can go ahead and say:

    use Tree::DAG_Node;
    my $root = Tree::DAG_Node->new();
    $root->name("I'm the tops");
    $new_daughter = Tree::DAG_Node->new();
    $new_daughter->name("More");
    $root->add_daughter($new_daughter);

  and so on, constructing and linking objects from Tree::DAG_Node and
  making useful tree structures out of them.


pkgId: e0d8d8367eaabf833f0f1123a0abd338a2790aca
name: local-perl-Tree-Simple-VisitorFactory
arch: src
version: 0.10
epoch: 0
release: 1
summary: Tree-Simple-VisitorFactory - A factory object for dispensing Visitor objects
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: stevan little <Eltstevan@iinteractive.comEgt>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Tree-Simple-VisitorFactory-0.10-1.src.rpm
checksum_type: sha
description:
  This object is really just a factory for dispensing Tree::Simple::Visitor::* objects. It is not required to use this package in order to use all the Visitors, it is just a somewhat convienient way to avoid having to type thier long class names.

  I considered making this a Singleton, but I did not because I thought that some people might not want that. I know that I am very picky about using Singletons, especially in multiprocess environments like mod_perl, so I implemented the smallest instance I knew how to, and made sure all other methods could be called as class methods too.


pkgId: 923e81ca335698c527e3b598c76acf3f573619ab
name: local-perl-Try-Tiny
arch: src
version: 0.09
epoch: 0
release: 1
summary: Try-Tiny - minimal try/catch with proper localization of $@
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Yuval Kogman <Eltnothingmuch@woobling.orgEgt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Try-Tiny-0.09-1.src.rpm
checksum_type: sha
description:
  This module provides bare bones C<try>/C<catch>/C<finally> statements that are designed to
  minimize common mistakes with eval blocks, and NOTHING else.

  This is unlike L<TryCatch> which provides a nice syntax and avoids adding
  another call stack layer, and supports calling C<return> from the try block to
  return from the parent subroutine. These extra features come at a cost of a few
  dependencies, namely L<Devel::Declare> and L<Scope::Upper> which are
  occasionally problematic, and the additional catch filtering uses L<Moose>
  type constraints which may not be desirable either.

  The main focus of this module is to provide simple and reliable error handling
  for those having a hard time installing L<TryCatch>, but who still want to
  write correct C<eval> blocks without 5 lines of boilerplate each time.

  It's designed to work as correctly as possible in light of the various
  pathological edge cases (see L<BACKGROUND>) and to be compatible with any style
  of error values (simple strings, references, objects, overloaded objects, etc).

  If the try block dies, it returns the value of the last statement executed in
  the catch block, if there is one. Otherwise, it returns C<undef> in scalar
  context or the empty list in list context. The following two examples both
  assign C<"bar"> to C<$x>.

  	my $x = try { die "foo" } catch { "bar" };

  	my $x = eval { die "foo" } || "bar";

  You can add finally blocks making the following true.

  	my $x;
  	try { die 'foo' } finally { $x = 'bar' };
  	try { die 'foo' } catch { warn "Got a die: $_" } finally { $x = 'bar' };

  Finally blocks are always executed making them suitable for cleanup code
  which cannot be handled using local.  You can add as many finally blocks to a
  given try block as you like.


pkgId: a4ac4cd51dc6570caa6cd0cfcb8a7842d17c317e
name: local-perl-UNIVERSAL-require
arch: src
version: 0.11
epoch: 0
release: 1
summary: UNIVERSAL-require - require() modules from a variable
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Michael G Schwern <schwern@pobox.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-UNIVERSAL-require-0.11-1.src.rpm
checksum_type: sha
description:
  If you've ever had to do this...

      eval "require $module";

  to get around the bareword caveats on require(), this module is for
  you.  It creates a universal require() class method that will work
  with every Perl module and its secure.  So instead of doing some
  arcane eval() work, you can do this:

      $module->require;

  It doesn't save you much typing, but it'll make alot more sense to
  someone who's not a ninth level Perl acolyte.


pkgId: d4f4d8f35050389cb1e6f5cb4a9f92722f40f958
name: local-perl-URI
arch: src
version: 1.35
epoch: 0
release: 8
summary: A Perl module implementing URI parsing and manipulation
url: http://search.cpan.org/dist/URI/
rpm_license: GPL+ or Artistic
rpm_group: Development/Libraries
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: local-perl-URI-1.35-8.src.rpm
checksum_type: sha
description:
  This module implements the URI class. Objects of this class represent
  "Uniform Resource Identifier references" as specified in RFC 2396 (and
  updated by RFC 2732).


pkgId: ce4dc3b78f40e5a36a2f98522bd3538919f40d09
name: local-perl-URI
arch: src
version: 1.37
epoch: 0
release: 1
summary: URI - Uniform Resource Identifiers (absolute and relative)
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: of the Arcadia <project@the>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-URI-1.37-1.src.rpm
checksum_type: sha
description:
  This module implements the C<URI> class.  Objects of this class
  represent "Uniform Resource Identifier references" as specified in RFC
  2396 (and updated by RFC 2732).

  A Uniform Resource Identifier is a compact string of characters that
  identifies an abstract or physical resource.  A Uniform Resource
  Identifier can be further classified as either a Uniform Resource Locator
  (URL) or a Uniform Resource Name (URN).  The distinction between URL
  and URN does not matter to the C<URI> class interface. A
  "URI-reference" is a URI that may have additional information attached
  in the form of a fragment identifier.

  An absolute URI reference consists of three parts:  a I<scheme>, a
  I<scheme-specific part> and a I<fragment> identifier.  A subset of URI
  references share a common syntax for hierarchical namespaces.  For
  these, the scheme-specific part is further broken down into
  I<authority>, I<path> and I<query> components.  These URIs can also
  take the form of relative URI references, where the scheme (and
  usually also the authority) component is missing, but implied by the
  context of the URI reference.  The three forms of URI reference
  syntax are summarized as follows:

    <scheme>:<scheme-specific-part>#<fragment>
    <scheme>://<authority><path>?<query>#<fragment>
    <path>?<query>#<fragment>

  The components into which a URI reference can be divided depend on the
  I<scheme>.  The C<URI> class provides methods to get and set the
  individual components.  The methods available for a specific
  C<URI> object depend on the scheme.


pkgId: 6333a9b1ca6c88fd52d069c691701b7da1d36362
name: local-perl-Unicode-CheckUTF8
arch: src
version: 1.01
epoch: 0
release: 1
summary: Unicode-CheckUTF8 - checks if scalar is valid UTF-8
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: bradfitz@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Unicode-CheckUTF8-1.01-1.src.rpm
checksum_type: sha
description:
  This is an XS wrapper around some Unicode Consortium code to check
  if a string is valid UTF-8, revised to conform to what expat/Mozilla
  think is valid UTF-8, especially with regard to low-ASCII characters.

  Note that this module has NOTHING to do with Perl's internal UTF8 flag
  on scalars.

  This module is for use when you're getting input from users and want
  to make sure it's valid UTF-8 before continuing.


pkgId: 836e462491dd8863c312d51981ea174efee5ea8a
name: local-perl-Unicode-Map
arch: src
version: 0.112
epoch: 0
release: 1
summary: Unicode-Map - maps charsets from and to utf16 unicode
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Martin Schwartz <EltFmartin@nacho.deEgt>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Unicode-Map-0.112-1.src.rpm
checksum_type: sha
description:
  This module converts strings from and to 2-byte Unicode UCS2 format.
  All mappings happen via 2 byte UTF16 encodings, not via 1 byte UTF8
  encoding. To transform these use Unicode::String.

  For historical reasons this module coexists with Unicode::Map8.
  Please use Unicode::Map8 unless you need to care for two byte character
  sets, e.g. chinese GB2312. Anyway, if you stick to the basic
  functionality (see documentation) you can use both modules equivalently.

  Practically this module will disappear from earth sooner or later as
  Unicode mapping support needs somehow to get into perl's core. If you
  like to work on this field please don't hesitate contacting Gisle Aas!

  This module can't deal directly with utf8. Use Unicode::String to convert
  utf8 to utf16 and vice versa.

  Character mapping is according to the data of binary mapfiles in Unicode::Map
  hierarchy. Binary mapfiles can also be created with this module, enabling you
  to install own specific character sets. Refer to mkmapfile or file REGISTRY in the Unicode::Map hierarchy.


pkgId: 0d5b7ce01bf78da8b456cb36a64ac1c6e94f81bd
name: local-perl-Unix-Syslog
arch: src
version: 1.1
epoch: 0
release: 1
summary: Unix-Syslog - Perl interface to the UNIX syslog(3) calls
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Marcus Harnisch <marcus.harnisch@gmx.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Unix-Syslog-1.1-1.src.rpm
checksum_type: sha
description:
  This module provides an interface to the system logger B<syslogd>(8) via
  Perl's XSUBs. The implementation attempts to resemble the native
  libc-functions of your system, so that anyone being familiar with
  F<syslog.h> should be able to use this module right away.

  In contrary to Sys::Syslog(3), this modules does not open a network
  connection to send the messages. This can help you to avoid opening
  security holes in your computer (see L<"FAQ">).

  The subs imported by the tag C<macros> are simply wrappers around the
  most important C<#defines> in your system's C header file
  F<syslog.h>. The macros return integer values that are used to specify
  options, facilities and priorities in a more or less portable
  way. They also provide general information about your local syslog
  mechanism. Check syslog(3) and your local F<syslog.h> for information
  about the macros, options and facilities available on your system.

  The following functions are provided:

  =over

  =item openlog $ident, $option, $facility

  opens a connection to the system logger.  I<$ident> is an identifier
  string that B<syslogd>(8) prints into every message. It usually equals
  the process name. I<$option> is an integer value that is the result of
  ORed options. I<$facility> is an integer value that specifies the part
  of the system the message should be associated with (e.g. kernel
  message, mail subsystem).

  =item syslog $priority, $format, @formatargs

  Generates a log message and passes it to the system logger. If
  C<syslog()> is called without calling C<openlog()> first, probably
  system dependent default values will be used as arguments for an
  implicit call to C<openlog()>.

  I<$priority> is an integer value that specifies the priority of the
  message. Alternatively I<$priority> can be the ORed value of a
  priority and a facility. In that case a previously selected facility
  will be overridden.

  In the case that C<syslog()> is called without calling C<openlog()>
  first and I<priority> does not specify both a priority I<and> a
  facility, a default facility will be used. This behaviour is most
  likely system dependent and the user should not rely on any particular
  value in that case.

  I<$format> is a format string in the style of printf(3). Additionally
  to the usual printf directives C<%m> can be specified in the
  string. It will be replaced implicitly by the contents of the Perl
  variable C<$!> (C<$ERRNO>). I<@formatargs> is a list of values that
  the format directives will be replaced with subsequently.

  =item closelog

  closes the connection to the system logger.

  =item setlogmask $mask_priority

  sets the priority mask and returns the old mask. Logging is enabled
  for the priorities indicated by the bits in the mask that are set and
  is disabled where the bits are not set. Macros are provided to specify
  valid and portable arguments to C<setlogmask()>. Usually the default
  log mask allows all messages to be logged.

  =item priorityname $priority

  returns a string containing the name of I<$priority> as string. If
  this functionality has not been enabled at installation, the function
  returns I<undef>.

  =item facilityname $facility

  returns a string containing the name of I<$facility> as string. If
  this functionality has not been enabled at installation, the function
  returns I<undef>.

  =back

  B<NOTE>: The behaviour of this module is system dependent. It is highly
  recommended to consult your system manual for available macros and the
  behaviour of the provided functions.


pkgId: d6c40b6477b3a53cb8075abf4dd0c7c950b7d472
name: local-perl-Variable-Magic
arch: src
version: 0.47
epoch: 0
release: 1
summary: Variable-Magic - Associate user-defined magic to variables from Perl.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Vincent Pit <perl@profvince.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Variable-Magic-0.47-1.src.rpm
checksum_type: sha
description:
  Magic is Perl's way of enhancing variables.
  This mechanism lets the user add extra data to any variable and hook syntactical operations (such as access, assignment or destruction) that can be applied to it.
  With this module, you can add your own magic to any variable without having to write a single line of XS.

  You'll realize that these magic variables look a lot like tied variables.
  It's not surprising, as tied variables are implemented as a special kind of magic, just like any 'irregular' Perl variable : scalars like C<$!>, C<$(> or C<$^W>, the C<%ENV> and C<%SIG> hashes, the C<@ISA> array,  C<vec()> and C<substr()> lvalues, L<threads::shared> variables...
  They all share the same underlying C API, and this module gives you direct access to it.

  Still, the magic made available by this module differs from tieing and overloading in several ways :

  =over 4

  =item *

  It isn't copied on assignment.

  You attach it to variables, not values (as for blessed references).

  =item *

  It doesn't replace the original semantics.

  Magic callbacks usually get triggered before the original action takes place, and can't prevent it from happening.
  This also makes catching individual events easier than with C<tie>, where you have to provide fallbacks methods for all actions by usually inheriting from the correct C<Tie::Std*> class and overriding individual methods in your own class.

  =item *

  It's type-agnostic.

  The same magic can be applied on scalars, arrays, hashes, subs or globs.
  But the same hook (see below for a list) may trigger differently depending on the the type of the variable.

  =item *

  It's mostly invisible at the Perl level.

  Magical and non-magical variables cannot be distinguished with C<ref>, C<tied> or another trick.

  =item *

  It's notably faster.

  Mainly because perl's way of handling magic is lighter by nature, and because there's no need for any method resolution.
  Also, since you don't have to reimplement all the variable semantics, you only pay for what you actually use.

  =back

  The operations that can be overloaded are :

  =over 4

  =item *

  C<get>

  This magic is invoked when the variable is evaluated.
  It is never called for arrays and hashes.

  =item *

  C<set>

  This one is triggered each time the value of the variable changes.
  It is called for array subscripts and slices, but never for hashes.

  =item *

  C<len>

  This magic is a little special : it is called when the 'size' or the 'length' of the variable has to be known by Perl.
  Typically, it's the magic involved when an array is evaluated in scalar context, but also on array assignment and loops (C<for>, C<map> or C<grep>).
  The callback has then to return the length as an integer.

  =item *

  C<clear>

  This magic is invoked when the variable is reset, such as when an array is emptied.
  Please note that this is different from undefining the variable, even though the magic is called when the clearing is a result of the undefine (e.g. for an array, but actually a bug prevent it to work before perl 5.9.5 - see the L<history|/PERL MAGIC HISTORY>).

  =item *

  C<free>

  This one can be considered as an object destructor.
  It happens when the variable goes out of scope, but not when it is undefined.

  =item *

  C<copy>

  This magic only applies to tied arrays and hashes.
  It fires when you try to access or change their elements.
  It is available on your perl iff C<MGf_COPY> is true.

  =item *

  C<dup>

  Invoked when the variable is cloned across threads.
  Currently not available.

  =item *

  C<local>

  When this magic is set on a variable, all subsequent localizations of the variable will trigger the callback.
  It is available on your perl iff C<MGf_LOCAL> is true.

  =back

  The following actions only apply to hashes and are available iff L</VMG_UVAR> is true.
  They are referred to as C<uvar> magics.

  =over 4

  =item *

  C<fetch>

  This magic happens each time an element is fetched from the hash.

  =item *

  C<store>

  This one is called when an element is stored into the hash.

  =item *

  C<exists>

  This magic fires when a key is tested for existence in the hash.

  =item *

  C<delete>

  This last one triggers when a key is deleted in the hash, regardless of whether the key actually exists in it.

  =back

  You can refer to the tests to have more insight of where the different magics are invoked.


pkgId: 715d791f5a83affc2f2233ddd8d21f54c96086e1
name: local-perl-Variable-Magic
arch: src
version: 0.52
epoch: 0
release: 1
summary: Variable-Magic - Associate user-defined magic to variables from Perl.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Vincent Pit <perl@profvince.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Variable-Magic-0.52-1.src.rpm
checksum_type: sha
description:
  Magic is Perl's way of enhancing variables.
  This mechanism lets the user add extra data to any variable and hook syntactical operations (such as access, assignment or destruction) that can be applied to it.
  With this module, you can add your own magic to any variable without having to write a single line of XS.

  You'll realize that these magic variables look a lot like tied variables.
  It is not surprising, as tied variables are implemented as a special kind of magic, just like any 'irregular' Perl variable : scalars like C<$!>, C<$(> or C<$^W>, the C<%ENV> and C<%SIG> hashes, the C<@ISA> array,  C<vec()> and C<substr()> lvalues, L<threads::shared> variables...
  They all share the same underlying C API, and this module gives you direct access to it.

  Still, the magic made available by this module differs from tieing and overloading in several ways :

  =over 4

  =item *

  Magic is not copied on assignment.

  You attach it to variables, not values (as for blessed references).

  =item *

  Magic does not replace the original semantics.

  Magic callbacks usually get triggered before the original action takes place, and cannot prevent it from happening.
  This also makes catching individual events easier than with C<tie>, where you have to provide fallbacks methods for all actions by usually inheriting from the correct C<Tie::Std*> class and overriding individual methods in your own class.

  =item *

  Magic is multivalued.

  You can safely apply different kinds of magics to the same variable, and each of them will be invoked successively.

  =item *

  Magic is type-agnostic.

  The same magic can be applied on scalars, arrays, hashes, subs or globs.
  But the same hook (see below for a list) may trigger differently depending on the the type of the variable.

  =item *

  Magic is invisible at Perl level.

  Magical and non-magical variables cannot be distinguished with C<ref>, C<tied> or another trick.

  =item *

  Magic is notably faster.

  Mainly because perl's way of handling magic is lighter by nature, and because there is no need for any method resolution.
  Also, since you don't have to reimplement all the variable semantics, you only pay for what you actually use.

  =back

  The operations that can be overloaded are :

  =over 4

  =item *

  I<get>

  This magic is invoked when the variable is evaluated.
  It is never called for arrays and hashes.

  =item *

  I<set>

  This magic is called each time the value of the variable changes.
  It is called for array subscripts and slices, but never for hashes.

  =item *

  I<len>

  This magic only applies to arrays (though it used to also apply to scalars), and is triggered when the 'size' or the 'length' of the variable has to be known by Perl.
  This is typically the magic involved when an array is evaluated in scalar context, but also on array assignment and loops (C<for>, C<map> or C<grep>).
  The length is returned from the callback as an integer.

  Starting from perl 5.12, this magic is no longer called by the C<length> keyword, and starting from perl 5.17.4 it is also no longer called for scalars in any situation, making this magic only meaningful on arrays.
  You can use the constants L</VMG_COMPAT_SCALAR_LENGTH_NOLEN> and L</VMG_COMPAT_SCALAR_NOLEN> to see if this magic is available for scalars or not.

  =item *

  I<clear>

  This magic is invoked when the variable is reset, such as when an array is emptied.
  Please note that this is different from undefining the variable, even though the magic is called when the clearing is a result of the undefine (e.g. for an array, but actually a bug prevent it to work before perl 5.9.5 - see the L<history|/PERL MAGIC HISTORY>).

  =item *

  I<free>

  This magic is called when a variable is destroyed as the result of going out of scope (but not when it is undefined).
  It behaves roughly like Perl object destructors (i.e. C<DESTROY> methods), except that exceptions thrown from inside a I<free> callback will always be propagated to the surrounding code.

  =item *

  I<copy>

  This magic only applies to tied arrays and hashes, and fires when you try to access or change their elements.

  =item *

  I<dup>

  This magic is invoked when the variable is cloned across threads.
  It is currently not available.

  =item *

  I<local>

  When this magic is set on a variable, all subsequent localizations of the variable will trigger the callback.
  It is available on your perl if and only if C<MGf_LOCAL> is true.

  =back

  The following actions only apply to hashes and are available if and only if L</VMG_UVAR> is true.
  They are referred to as I<uvar> magics.

  =over 4

  =item *

  I<fetch>

  This magic is invoked each time an element is fetched from the hash.

  =item *

  I<store>

  This one is called when an element is stored into the hash.

  =item *

  I<exists>

  This magic fires when a key is tested for existence in the hash.

  =item *

  I<delete>

  This magic is triggered when a key is deleted in the hash, regardless of whether the key actually exists in it.

  =back

  You can refer to the tests to have more insight of where the different magics are invoked.


pkgId: 2a9b69cb48d1f45e888f3fc4b8d7d1c99e44393e
name: local-perl-WWW-Mechanize
arch: src
version: 1.34
epoch: 0
release: 1
summary: WWW-Mechanize - Handy web browsing in a Perl object
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Andy Lester <andy@petdance.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-WWW-Mechanize-1.34-1.src.rpm
checksum_type: sha
description:
  C<WWW::Mechanize>, or Mech for short, helps you automate interaction with
  a website. It supports performing a sequence of page fetches including
  following links and submitting forms. Each fetched page is parsed and
  its links and forms are extracted. A link or a form can be selected, form
  fields can be filled and the next page can be fetched. Mech also stores
  a history of the URLs you've visited, which can be queried and revisited.

      use WWW::Mechanize;
      my $mech = WWW::Mechanize->new();

      $mech->get( $url );

      $mech->follow_link( n => 3 );
      $mech->follow_link( text_regex => qr/download this/i );
      $mech->follow_link( url => 'http://host.com/index.html' );

      $mech->submit_form(
          form_number => 3,
          fields      => {
              username    => 'mungo',
              password    => 'lost-and-alone',
          }
      );

      $mech->submit_form(
          form_name => 'search',
          fields    => { query  => 'pot of gold', },
          button    => 'Search Now'
      );


  Mech is well suited for use in testing web applications.  If you use
  one of the Test::*, like L<Test::HTML::Lint> modules, you can check the
  fetched content and use that as input to a test call.

      use Test::More;
      like( $mech->content(), qr/$expected/, "Got expected content" );

  Each page fetch stores its URL in a history stack which you can
  traverse.

      $mech->back();

  If you want finer control over your page fetching, you can use
  these methods. C<follow_link> and C<submit_form> are just high
  level wrappers around them.

      $mech->find_link( n => $number );
      $mech->form_number( $number );
      $mech->form_name( $name );
      $mech->field( $name, $value );
      $mech->set_fields( %field_values );
      $mech->set_visible( @criteria );
      $mech->click( $button );

  L<WWW::Mechanize> is a proper subclass of L<LWP::UserAgent> and
  you can also use any of L<LWP::UserAgent>'s methods.

      $mech->add_header($name => $value);

  Please note that Mech does NOT support JavaScript.  Please check the
  FAQ in WWW::Mechanize::FAQ for more.


pkgId: 37e579f9b844faed4e7dca9e4732df3f984a1b0d
name: local-perl-Want
arch: src
version: 0.18
epoch: 0
release: 1
summary: Want - A generalisation of C<wantarray>
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Robin Houston <Eltrobin@cpan.orgEgt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-Want-0.18-1.src.rpm
checksum_type: sha
description:
  This module generalises the mechanism of the B<wantarray> function,
  allowing a function to determine in some detail how its return value
  is going to be immediately used.


pkgId: 995b7ba8d25a5ebfab291f31435c235d826a1964
name: local-perl-XML-Atom-Syndication
arch: src
version: 0.942
epoch: 0
release: 1
summary: XML-Atom-Syndication - a portable client for
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Timothy Appnel <tima@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-Atom-Syndication-0.942-1.src.rpm
checksum_type: sha
description:
  This project is the result of scratching ones own itch. I
  was writing some web software needed a full-featured library
  for working with Atom feeds that was easy to distribute and
  install on wide range of environments. Many of my software's
  target audience are relative novices working with low-cost
  shared hosting environments. (A significant number don't
  even have shell access!) Creating a library that was easy to
  install even by FTP was a paramount requirement that many
  other options failed to meet.

  Originally the module began as a very spartan XPath driven
  interface. At the time the format had just been introduced
  and was still vague and very extremely volatile. It was a
  pretty wretched piece of software, but it got me through
  while the Atom Working Group worked out the details of the
  Atom Syndication Format.

  Since that time the Atom Syndication Format (ASF) has made
  its way through numerous drafts and is now an approved
  standard of the IETF as RFC 4287.

  Beginning with version 0.9, XML::Atom::Syndication has been
  completely rewritten to provide better functionality and
  structure in working with a stable Atom format
  specification.

  The interface and a fair bit of the code was based on that
  of L<XML::Atom>. It owes a great deal to its authors, Ben
  Trott and Tatsuhiko Miyagawa, and all its contributors.

  As of version 0.16, XML::Atom defaults to version 0.3 which
  is now deprecated.  Baseline 1.0 support has been built-in
  however many of the changes that were introduced (category
  elements, dropping the mode attribute in the content
  construct) have yet to be implemented. I'm sure this will
  change eventually, but it currently is a differentiator
  between the two implementations. XML::Atom::Syndication
  supports 0.3, but defaults 1.0.

  More importantly this implementation is not tied to specific
  XML parsers -- XML::LibXML or XML::XPath (expat) as is the
  case with XML::Atom. Both of these parsers libraries require
  compilation  which can be a major hurdle if you are not in
  charge of your hosting environment. By using SAX at the
  core, this Atom implementation will work with whatever
  parser it can find including the default pure perl option
  that XML::SAX is distributed with.

  Unlike XML::Atom, this distribution focuses on the Atom
  syndication format and not the publishing protocol. The
  publishing protocol is still being worked out and is not an
  official standard at this time.


pkgId: a544d6966fa7a02f291ac0d2db82b34bdee7d17e
name: local-perl-XML-DOM
arch: src
version: 1.44
epoch: 0
release: 1
summary: XML-DOM - A perl module for building DOM Level 1 compliant document structures
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: patches to TJ <Mather@Ftjmather@maxmind.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-DOM-1.44-1.src.rpm
checksum_type: sha
description:
  This module extends the XML::Parser module by Clark Cooper.
  The XML::Parser module is built on top of XML::Parser::Expat,
  which is a lower level interface to James Clark's expat library.

  XML::DOM::Parser is derived from XML::Parser. It parses XML strings or files
  and builds a data structure that conforms to the API of the Document Object
  Model as described at http://www.w3.org/TR/REC-DOM-Level-1.
  See the XML::Parser manpage for other available features of the
  XML::DOM::Parser class.
  Note that the 'Style' property should not be used (it is set internally.)

  The XML::Parser I<NoExpand> option is more or less supported, in that it will
  generate EntityReference objects whenever an entity reference is encountered
  in character data. I'm not sure how useful this is. Any comments are welcome.

  As described in the synopsis, when you create an XML::DOM::Parser object,
  the parse and parsefile methods create an I<XML::DOM::Document> object
  from the specified input. This Document object can then be examined, modified and
  written back out to a file or converted to a string.

  When using XML::DOM with XML::Parser version 2.19 and up, setting the
  XML::DOM::Parser option I<KeepCDATA> to 1 will store CDATASections in
  CDATASection nodes, instead of converting them to Text nodes.
  Subsequent CDATASection nodes will be merged into one. Let me know if this
  is a problem.

  When using XML::Parser 2.27 and above, you can suppress expansion of
  parameter entity references (e.g. %pent;) in the DTD, by setting I<ParseParamEnt>
  to 1 and I<ExpandParamEnt> to 0. See L<Hidden Nodes|/_Hidden_Nodes_> for details.

  A Document has a tree structure consisting of I<Node> objects. A Node may contain
  other nodes, depending on its type.
  A Document may have Element, Text, Comment, and CDATASection nodes.
  Element nodes may have Attr, Element, Text, Comment, and CDATASection nodes.
  The other nodes may not have any child nodes.

  This module adds several node types that are not part of the DOM spec (yet.)
  These are: ElementDecl (for <!ELEMENT ...> declarations), AttlistDecl (for
  <!ATTLIST ...> declarations), XMLDecl (for <?xml ...?> declarations) and AttDef
  (for attribute definitions in an AttlistDecl.)


pkgId: bcb3ececd77e31bf3314d8a17391f0625c751b52
name: local-perl-XML-Dumper
arch: src
version: 0.81
epoch: 0
release: 1
summary: XML-Dumper - Perl module for dumping Perl objects from/to XML
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: mikewong@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-Dumper-0.81-1.src.rpm
checksum_type: sha
description:
  XML::Dumper dumps Perl data to XML format. XML::Dumper can also read XML data
  that was previously dumped by the module and convert it back to Perl. You can
  use the module read the XML from a file and write the XML to a file. Perl
  objects are blessed back to their original packaging; if the modules are
  installed on the system where the perl objects are reconstituted from xml, they
  will behave as expected. Intuitively, if the perl objects are converted and
  reconstituted in the same environment, all should be well. And it is.

  Additionally, because XML benefits so nicely from compression, XML::Dumper
  understands gzipped XML files. It does so with an optional dependency on
  Compress::Zlib. So, if you dump a Perl variable with a file that has an
  extension of '.xml.gz', it will store and compress the file in gzipped format.
  Likewise, if you read a file with the extension '.xml.gz', it will uncompress
  the file in memory before parsing the XML back into a Perl variable.

  Another fine challenge that this module rises to meet is that it understands
  circular definitions and multiple references to a single object. This includes
  doubly-linked lists, circular references, and the so-called 'Flyweight' pattern of
  Object Oriented programming. So it can take the gnarliest of your perl data, and
  should do just fine.

  One caveat; XML::Dumper does not handle binary data. There have been
  discussions in the expat mailing list archives discussing the challenges
  associated with encoding binary data with XML. I chose the cowardly path
  of making the problem a non-issue by not addressing it. To store binary
  data, one could encode the data into ASCII before encapsulating the data
  as XML, and then reverse the process to restore the data. There are several
  Perl modules that one can use for this, Convert::UU, for example.


pkgId: 57e493c59113016ae5c0cafabd5cec66bdd51754
name: local-perl-XML-Elemental
arch: src
version: 2.1
epoch: 0
release: 1
summary: XML-Elemental - simplistic and perlish handling of XML
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Timothy Appnel <tima@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-Elemental-2.1-1.src.rpm
checksum_type: sha
description:
  XML::Elemental is a SAX-based package for easily parsing XML
  documents into a more native and mostly object-oriented perl
  form.

  The development of this package grew out of the desire for
  something more object-oriented then L<XML::Simple> and was
  more simplistic and perlish then the various standard XML
  API modules such as L<XML::DOM>. Easier installation of
  modules was also a contributing factor.

  Original this package began as a style plugin to
  L<XML::Parser>. That proved to be too limiting that it was
  expanded. With the release of version 2.0 the package was
  refactored to take advantage of any parser supporting SAX
  that includes the pure perl option that ships with
  L<XML::SAX>.


pkgId: 36c524fafc0ee9c37ff7ba917a90f08a01fb49ed
name: local-perl-XML-Feed
arch: src
version: 0.42
epoch: 0
release: 1
summary: XML-Feed - Syndication feed parser and auto-discovery
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Six Apart <cpan@sixapart.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-Feed-0.42-1.src.rpm
checksum_type: sha
description:
  I<XML::Feed> is a syndication feed parser for both RSS and Atom feeds. It
  also implements feed auto-discovery for finding feeds, given a URI.

  I<XML::Feed> supports the following syndication feed formats:

  =over 4

  =item * RSS 0.91

  =item * RSS 1.0

  =item * RSS 2.0

  =item * Atom

  =back

  The goal of I<XML::Feed> is to provide a unified API for parsing and using
  the various syndication formats. The different flavors of RSS and Atom
  handle data in different ways: date handling; summaries and content;
  escaping and quoting; etc. This module attempts to remove those differences
  by providing a wrapper around the formats and the classes implementing
  those formats (I<XML::RSS> and I<XML::Atom::Feed>). For example, dates are
  handled differently in each of the above formats. To provide a unified API for
  date handling, I<XML::Feed> converts all date formats transparently into
  I<DateTime> objects, which it then returns to the caller.


pkgId: d835d20bf1eefa8cc24ef21717271429530a3211
name: local-perl-XML-FeedPP
arch: src
version: 0.40
epoch: 0
release: 1
summary: XML-FeedPP - - Parse/write/merge/edit RSS/RDF/Atom syndication feeds
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Yusuke Kawasaki httpwwwkawanet <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-FeedPP-0.40-1.src.rpm
checksum_type: sha
description:
  C<XML::FeedPP> is an all-purpose syndication utility that parses and
  publishes RSS 2.0, RSS 1.0 (RDF), Atom 0.3 and 1.0 feeds.
  It allows you to add new content, merge feeds, and convert among
  these various formats.
  It is a pure Perl implementation and does not require any other
  module except for XML::TreePP.


pkgId: 6388f1667e7a1ab7b4744ca4db6bee12f5d9a9ea
name: local-perl-XML-LibXML
arch: src
version: 1.66
epoch: 1
release: 2
summary: Perl interface to the libxml2 library
url: http://search.cpan.org/dist/XML-LibXML/
rpm_license: GPL+ or Artistic
rpm_group: Development/Libraries
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: local-perl-XML-LibXML-1.66-2.src.rpm
checksum_type: sha
description:
  This module implements a Perl interface to the GNOME libxml2 library
  which provides interfaces for parsing and manipulating XML files. This
  module allows Perl programmers to make use of the highly capable
  validating XML parser and the high performance DOM implementation.


pkgId: 3031113adeb699e77d9e48c0ee7e04f157423309
name: local-perl-XML-LibXML-Common
arch: src
version: 0.13
epoch: 0
release: 1
summary: XML-LibXML-Common - Routines and Constants common for XML::LibXML and XML::GDOME
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Christian Glahn <christian.glahn@uibk.ac.at>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-LibXML-Common-0.13-1.src.rpm
checksum_type: sha
description:
  XML::LibXML and XML::GDOME share some of the same functionality. This
  package should bundle some shared constansts and functions, so both
  modules may coexist within the same scripts.

  XML::LibXML::Common defines all node types as constants. While
  XML::LibXML and XML::GDOME originally declared their own node type
  definitions, one may want to use XML::LibXML::Common in its
  compatibility mode:

  =over 4

  =item * use XML::LibXML::Common qw(:libxml);

  :libxml will use the XML::LibXML Compatibility mode, which defines the
  old 'XML_' node-type definitions

  =item * use XML::LibXML::Common qw(:gdome);

  This allows one to use the XML::LibXML Compatibility mode, which
  defines the old 'GDOME_' node-type definitions

  =item * use XML::LibXML::Common qw(:w3c);

  This uses the nodetype definition names as specified for DOM.

  =item * use XML::LibXML::Common qw(:encoding);

  This is ment if only the encoding functions of XML::LibXML::Common
  should be used.

  =back

  By default the W3 definitions as defined in the DOM specifications and
  the encoding functions are exported by XML::LibXML::Common.


pkgId: f686be27a27fff7e48e0ba664d372d1e88ea8db3
name: local-perl-XML-LibXSLT
arch: src
version: 1.62
epoch: 0
release: 1
summary: XML-LibXSLT - Interface to Gnome libxslt library
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Matt Sergeant
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-LibXSLT-1.62-1.src.rpm
checksum_type: sha
description:
  This module is an interface to the gnome project's libxslt. This is an
  extremely good XSLT engine, highly compliant and also very fast. I have
  tests showing this to be more than twice as fast as Sablotron.


pkgId: b911fe1becb6078bd68ee9c152e119b0123e9ec5
name: local-perl-XML-NamespaceSupport
arch: src
version: 1.09
epoch: 0
release: 1
summary: XML-NamespaceSupport - a simple generic namespace support class
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Robin Berjon <robin@knowscape.com,>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-NamespaceSupport-1.09-1.src.rpm
checksum_type: sha
description:
  This module offers a simple to process namespaced XML names (unames)
  from within any application that may need them. It also helps maintain
  a prefix to namespace URI map, and provides a number of basic checks.

  The model for this module is SAX2's NamespaceSupport class, readable at
  http://www.megginson.com/SAX/Java/javadoc/org/xml/sax/helpers/NamespaceSupport.html.
  It adds a few perlisations where we thought it appropriate.


pkgId: 783fbce4a944521246da48442007ed86fa976ba1
name: local-perl-XML-Parser
arch: src
version: 2.36
epoch: 0
release: 1
summary: XML-Parser - A perl module for parsing XML documents
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Clark Cooper (coopercc@netheaven.com)
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-Parser-2.36-1.src.rpm
checksum_type: sha
description:
  This module provides ways to parse XML documents. It is built on top of
  L<XML::Parser::Expat>, which is a lower level interface to James Clark's
  expat library. Each call to one of the parsing methods creates a new
  instance of XML::Parser::Expat which is then used to parse the document.
  Expat options may be provided when the XML::Parser object is created.
  These options are then passed on to the Expat object on each parse call.
  They can also be given as extra arguments to the parse methods, in which
  case they override options given at XML::Parser creation time.

  The behavior of the parser is controlled either by C<L</Style>> and/or
  C<L</Handlers>> options, or by L</setHandlers> method. These all provide
  mechanisms for XML::Parser to set the handlers needed by XML::Parser::Expat.
  If neither C<Style> nor C<Handlers> are specified, then parsing just
  checks the document for being well-formed.

  When underlying handlers get called, they receive as their first parameter
  the I<Expat> object, not the Parser object.


pkgId: 2928b8a3765ae060cbab980537ba72094840b4cc
name: local-perl-XML-Pastor
arch: src
version: 1.0.3
epoch: 0
release: 1
summary: XML-Pastor - Generate Perl classes with XML bindings starting from a W3C XSD Schema
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Ayhan Ulusoy <dev@ulusoy.name>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build32
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-Pastor-1.0.3-1.src.rpm
checksum_type: sha
description:
  Java had CASTOR, and now Perl has B<XML::Pastor>!

  If you know what Castor does in the Java world, then B<XML::Pastor> should be familiar to you. If you have a B<W3C XSD schema>,
  you can generate Perl classes with roundtrip XML bindings.

  Whereas Castor is limited to offline code generation, B<XML::Pastor> is able to generate Perl classes
  either offline or at run-time starting from a W3C XSD Schema. The generated classes correspond to
  the global elements, complex and simple type declarations in the schema. The generated classes have full XML binding,
  meaning objects belonging to them can be read from and written to XML. Accessor methods for attributes and child elements will be generated automatically.
  Furthermore it is possible to validate the objects of generated classes against the original schema although the schema is typically no longer accessible.

  B<XML::Pastor> defines just one method, 'I<generate()>', but the classes it generates define many methods which may
  be found in the documentation of L<XML::Pastor::ComplexType> and L<XML::Pastor::SimpleType> from which all generated classes
  descend.

  In 'I<offline>'  mode, it is possible to generate a single module with all the generated clasess or multiple modules
  one for each class. The typical use of the offline mode is during a 'make' process, where you have a set of XSD schemas and you
  generate your modules to be later installed by the 'make install'. This is very similar to Java Castor's behaviour.
  This way your XSD schemas don't have to be accessible during run-time and you don't have a performance penalty.

  Perl philosophy dictates however, that There Is More Than One Way To Do It. In 'I<eval>' (run-time) mode, the XSD schema is processed at
  run-time giving much more flexibility to the user. This added flexibility has a price on the other hand, namely a performance penalty and
  the fact that the XSD schema needs to be accessible at run-time. Note that the performance penalty applies only to the code genereration (pastorize) phase;
  the generated classes perform the same as if they were generated offline.

  There is a command line utility called L<pastorize> that can help generating classes offline. See the documentation of L<pastorize> for more details on that.


pkgId: d9c0afbe6026954f490f998fda98cc6abf85bb74
name: local-perl-XML-RPC
arch: src
version: 0.9
epoch: 0
release: 1
summary: XML-RPC - Pure Perl implementation for an XML-RPC client and server
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Niek Albers
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-RPC-0.9-1.src.rpm
checksum_type: sha
description:
  XML::RPC module provides simple Pure Perl methods for XML-RPC communication.
  It's goals are simplicity and flexibility. XML::RPC uses XML::TreePP
  for parsing.


pkgId: 2f764a859fd235eddfe6ca9c627697f7388cdb91
name: local-perl-XML-RSS
arch: src
version: 1.33
epoch: 0
release: 1
summary: XML-RSS - creates and updates RSS files
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: code Jonathan Eisenzopf <eisen@pobox.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-RSS-1.33-1.src.rpm
checksum_type: sha
description:
  This module provides a basic framework for creating and maintaining
  RDF Site Summary (RSS) files. This distribution also contains many
  examples that allow you to generate HTML from an RSS, convert between
  0.9, 0.91, and 1.0 version, and other nifty things.
  This might be helpful if you want to include news feeds on your Web
  site from sources like Slashdot and Freshmeat or if you want to syndicate
  your own content.

  XML::RSS currently supports 0.9, 0.91, and 1.0 versions of RSS.
  See http://backend.userland.com/rss091 for information on RSS 0.91.
  See http://www.purplepages.ie/RSS/netscape/rss0.90.html for RSS 0.9.
  See http://web.resource.org/rss/1.0/ for RSS 1.0.

  RSS was originally developed by Netscape as the format for
  Netscape Netcenter channels, however, many Web sites have since
  adopted it as a simple syndication format. With the advent of RSS 1.0,
  users are now able to syndication many different kinds of content
  including news headlines, threaded measages, products catalogs, etc.


pkgId: 0722597c935a53ac118cf2d196586426014a737d
name: local-perl-XML-RegExp
arch: src
version: 0.02
epoch: 0
release: 1
summary: XML-RegExp - Regular expressions for XML tokens
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: tjmather@cpan.org
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-RegExp-0.02-1.src.rpm
checksum_type: sha
description:
  This package contains regular expressions for the following XML tokens:
  BaseChar, Ideographic, Letter, Digit, Extender, CombiningChar, NameChar,
  EntityRef, CharRef, Reference, Name, NmToken, and AttValue.

  The definitions of these tokens were taken from the XML spec
  (Extensible Markup Language 1.0) at L<http://www.w3.org/TR/REC-xml>.

  Also contains the regular expressions for the following tokens from the
  XML Namespaces spec at L<http://www.w3.org/TR/REC-xml-names>:
  NCNameChar, NCName, QName, Prefix and LocalPart.


pkgId: aa185e81bc7363a6c51b07f2dd249c4d303b25b1
name: local-perl-XML-SAX
arch: src
version: 0.96
epoch: 0
release: 1
summary: XML-SAX - Simple API for XML
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: maintainer Grant McLean <grantm@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-SAX-0.96-1.src.rpm
checksum_type: sha
description:
  XML::SAX is a SAX parser access API for Perl. It includes classes
  and APIs required for implementing SAX drivers, along with a factory
  class for returning any SAX parser installed on the user's system.


pkgId: 31e90bfaa17d9b3848f8d26637e098cd94735e53
name: local-perl-XML-SAX-PurePerl
arch: src
version: 0.80
epoch: 0
release: 1
summary: XML-SAX-PurePerl - Pure Perl XML Parser with SAX2 interface
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Matt Sergeant, matt@sergeant.org
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-SAX-PurePerl-0.80-1.src.rpm
checksum_type: sha
description:
  This module implements an XML parser in pure perl. It is written around the upcoming
  perl 5.8's unicode support and support for multiple document encodings (using the
  PerlIO layer), however it has been ported to work with ASCII documents under lesser
  perl versions.

  The SAX2 API is described in detail at http://sourceforge.net/projects/perl-xml/, in
  the CVS archive, under libxml-perl/docs. Hopefully those documents will be in a
  better location soon.

  Please refer to the SAX2 documentation for how to use this module - it is merely a
  front end to SAX2, and implements nothing that is not in that spec (or at least tries
  not to - please email me if you find errors in this implementation).


pkgId: d21403c829cb43f7c2be8f0293804f41b5825ded
name: local-perl-XML-Simple
arch: src
version: 2.18
epoch: 0
release: 1
summary: XML-Simple - Easy API to maintain XML (esp config files)
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Grant McLean <grantm@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-Simple-2.18-1.src.rpm
checksum_type: sha
description:
  The XML::Simple module provides a simple API layer on top of an underlying XML
  parsing module (either XML::Parser or one of the SAX2 parser modules).  Two
  functions are exported: C<XMLin()> and C<XMLout()>.  Note: you can explicity
  request the lower case versions of the function names: C<xml_in()> and
  C<xml_out()>.

  The simplest approach is to call these two functions directly, but an
  optional object oriented interface (see L<"OPTIONAL OO INTERFACE"> below)
  allows them to be called as methods of an B<XML::Simple> object.  The object
  interface can also be used at either end of a SAX pipeline.


pkgId: 010d686595feb06185718c7da1b9500f08a304a1
name: local-perl-XML-Stream
arch: src
version: 1.22
epoch: 0
release: 1
summary: XML-Stream - Creates and XML Stream connection and parses return data
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: by Ryan Eatmon <reatmon@ti.com>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-Stream-1.22-1.src.rpm
checksum_type: sha
description:
  This module provides the user with methods to connect to a remote
    server, send a stream of XML to the server, and receive/parse an XML
    stream from the server.  It is primarily based work for the Etherx XML
    router developed by the Jabber Development Team.  For more information
    about this project visit http://etherx.jabber.org/stream/.

    XML::Stream gives the user the ability to define a central callback
    that will be used to handle the tags received from the server.  These
    tags are passed in the format defined at instantiation time.
    the closing tag of an object is seen, the tree is finished and passed
    to the call back function.  What the user does with it from there is up
    to them.

    For a detailed description of how this module works, and about the data
    structure that it returns, please view the source of Stream.pm and
    look at the detailed description at the end of the file.


    NOTE: The parser that XML::Stream::Parser provides, as are most Perl
    parsers, is synchronous.  If you are in the middle of parsing a
    packet and call a user defined callback, the Parser is blocked until
    your callback finishes.  This means you cannot be operating on a
    packet, send out another packet and wait for a response to that packet.
    It will never get to you.  Threading might solve this, but as we all
    know threading in Perl is not quite up to par yet.  This issue will be
    revisted in the future.


pkgId: ab0937a6194050c4277818b4be4ee479cbe48d5e
name: local-perl-XML-TreeBuilder
arch: src
version: 3.09
epoch: 0
release: 1
summary: XML-TreeBuilder - Parser that builds a tree of XML::Element objects
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sean M Burke <Eltsburke@cpan.orgEgt>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-TreeBuilder-3.09-1.src.rpm
checksum_type: sha
description:
  This module uses XML::Parser to make XML document trees constructed of
  XML::Element objects (and XML::Element is a subclass of HTML::Element
  adapted for XML).  XML::TreeBuilder is meant particularly for people
  who are used to the HTML::TreeBuilder / HTML::Element interface to
  document trees, and who don't want to learn some other document
  interface like XML::Twig or XML::DOM.

  The way to use this class is to:

  1. start a new (empty) XML::TreeBuilder object.

  2. set any of the "store" options you want.

  3. then parse the document from a source by calling
  C<$x-E<gt>parsefile(...)>
  or
  C<$x-E<gt>parse(...)> (See L<XML::Parser> docs for the options
  that these two methods take)

  4. do whatever you need to do with the syntax tree, presumably
  involving traversing it looking for some bit of information in it,

  5. and finally, when you're done with the tree, call $tree->delete to
  erase the contents of the tree from memory.  This kind of thing
  usually isn't necessary with most Perl objects, but it's necessary for
  TreeBuilder objects.  See L<HTML::Element> for a more verbose
  explanation of why this is the case.


pkgId: 95977fd39037da6d6eb61cbe9eb747b848620402
name: local-perl-XML-TreePP
arch: src
version: 0.38
epoch: 0
release: 1
summary: XML-TreePP - - Pure Perl implementation for parsing/writing XML documents
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Yusuke Kawasaki httpwwwkawanet <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-TreePP-0.38-1.src.rpm
checksum_type: sha
description:
  XML::TreePP module parses an XML document and expands it for a hash tree.
  This generates an XML document from a hash tree as the opposite way around.
  This is a pure Perl implementation and requires no modules depended.
  This can also fetch and parse an XML document from remote web server
  like the XMLHttpRequest object does at JavaScript language.


pkgId: 7a3a524b3c8770f0b64398a450992e38e4ced931
name: local-perl-XML-Twig
arch: src
version: 3.32
epoch: 0
release: 1
summary: XML-Twig - XML, The Perl Way
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Michel Rodriguez <mirod@xmltwig.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-Twig-3.32-1.src.rpm
checksum_type: sha
description:
  This module provides a way to process XML documents. It is build on top
  of C<XML::Parser>.

  The module offers a tree interface to the document, while allowing you
  to output the parts of it that have been completely processed.

  It allows minimal resource (CPU and memory) usage by building the tree
  only for the parts of the documents that need actual processing, through the
  use of the C<L<twig_roots|twig_roots> > and
  C<L<twig_print_outside_roots|twig_print_outside_roots> > options. The
  C<L<finish|finish> > and C<L<finish_print|finish_print> > methods also help
  to increase performances.

  XML::Twig tries to make simple things easy so it tries its best to takes care
  of a lot of the (usually) annoying (but sometimes necessary) features that
  come with XML and XML::Parser.


pkgId: 85a56e1cadbb23813c6d43b869b93bdefee56e24
name: local-perl-XML-Twig
arch: src
version: 3.37
epoch: 0
release: 1
summary: XML-Twig - XML, The Perl Way
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Michel Rodriguez <mirod@xmltwig.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-Twig-3.37-1.src.rpm
checksum_type: sha
description:
  This module provides a way to process XML documents. It is build on top
  of C<XML::Parser>.

  The module offers a tree interface to the document, while allowing you
  to output the parts of it that have been completely processed.

  It allows minimal resource (CPU and memory) usage by building the tree
  only for the parts of the documents that need actual processing, through the
  use of the C<L<twig_roots> > and
  C<L<twig_print_outside_roots> > options. The
  C<L<finish> > and C<L<finish_print> > methods also help
  to increase performances.

  XML::Twig tries to make simple things easy so it tries its best to takes care
  of a lot of the (usually) annoying (but sometimes necessary) features that
  come with XML and XML::Parser.


pkgId: b2391b1fea2c52b4dae2831753cdccb815e2c1cf
name: local-perl-XML-Writer
arch: src
version: 0.604
epoch: 0
release: 1
summary: XML-Writer - Perl extension for writing XML documents.
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: David Megginson <Eltdavid@megginson.comEgt>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-Writer-0.604-1.src.rpm
checksum_type: sha
description:
  XML::Writer is a helper module for Perl programs that write an XML
  document.  The module handles all escaping for attribute values and
  character data and constructs different types of markup, such as tags,
  comments, and processing instructions.

  By default, the module performs several well-formedness checks to
  catch errors during output.  This behaviour can be extremely useful
  during development and debugging, but it can be turned off for
  production-grade code.

  The module can operate either in regular mode in or Namespace
  processing mode.  In Namespace mode, the module will generate
  Namespace Declarations itself, and will perform additional checks on
  the output.

  Additional support is available for a simplified data mode with no
  mixed content: newlines are automatically inserted around elements and
  elements can optionally be indented based as their nesting level.


pkgId: 8f446d07b765945b9a8d167d85355a9ba63d53ce
name: local-perl-XML-XPath
arch: src
version: 1.13
epoch: 0
release: 1
summary: XML-XPath - a set of modules for parsing and evaluating XPath statements
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Matt Sergeant, AxKit.com Ltd
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XML-XPath-1.13-1.src.rpm
checksum_type: sha
description:
  This module aims to comply exactly to the XPath specification at
  http://www.w3.org/TR/xpath and yet allow extensions to be added in the
  form of functions. Modules such as XSLT and XPointer may need to do
  this as they support functionality beyond XPath.


pkgId: a13f69b2f24d603e0190a76a81202f638d561498
name: local-perl-XSLoader
arch: src
version: 0.10
epoch: 0
release: 1
summary: XSLoader - Dynamically load C libraries into Perl code
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sebastien Aperghis-Tramoni <sebastien@aperghis.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-XSLoader-0.10-1.src.rpm
checksum_type: sha
description:
  This module defines a standard I<simplified> interface to the dynamic
  linking mechanisms available on many platforms.  Its primary purpose is
  to implement cheap automatic dynamic loading of Perl modules.

  For a more complicated interface, see L<DynaLoader>.  Many (most)
  features of C<DynaLoader> are not implemented in C<XSLoader>, like for
  example the C<dl_load_flags>, not honored by C<XSLoader>.


pkgId: e582a8531cd228e4f671e29417250183427a6c85
name: local-perl-common-sense
arch: src
version: 0.04
epoch: 0
release: 1
summary: common-sense - save a tree AND a kitten, use common::sense!
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Marc Lehmann <schmorp@schmorp.de>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-common-sense-0.04-1.src.rpm
checksum_type: sha
description:
  This module implements some sane defaults for Perl programs, as defined by
  two typical (or not so typical - use your common sense) specimens of
  Perl coders.

  =over 4

  =item no warnings

  The dreaded warnings. Even worse, the horribly dreaded C<-w> switch. Even
  though we don't care if other people use warnings (and certainly there are
  useful ones), a lot of warnings simply go against the spirit of Perl, most
  prominently, the warnings related to C<undef>. There is nothing wrong with
  C<undef>: it has well-defined semantics, it is useful, and spitting out
  warnings you never asked for is just evil.

  So every module needs C<no warnings> to avoid somebody accidentally using
  C<-w> and forcing his bad standards on our code. No will do.

  Funnily enough, L<perllexwarn> explicitly mentions C<-w> (and not in a
  favourable way), but standard utilities, such as L<prove>, or MakeMaker
  when running C<make test> enable them blindly.

  =item use strict qw(subs vars)

  Using C<use strict> is definitely common sense, but C<use strict
  'refs'> definitely overshoots it's usefulness. After almost two
  decades of Perl hacking, we decided that it does more harm than being
  useful. Specifically, constructs like these:

     @{ $var->[0] }

  Must be written like this (or similarly), when C<use strict 'refs'> is in
  scope, and C<$var> can legally be C<undef>:

     @{ $var->[0] || [] }

  This is annoying, and doesn't shield against obvious mistakes such as
  using C<"">, so one would even have to write:

     @{ defined $var->[0] ? $var->[0] :  [] }

  ... which nobody with a bit of common sense would consider
  writing. Curiously enough, sometimes, perl is not so strict, as this works
  even with C<use strict> in scope:

     for (@{ $var->[0] }) { ...

  If that isnt hipocrasy! And all that from a mere program!

  =item use feature qw(say state given)

  We found it annoying that we always have to enable extra features. If
  something breaks because it didn't anticipate future changes, so be
  it. 5.10 broke almost all our XS modules and nobody cared either - and few
  modules that are no longer maintained work with newer versions of Perl,
  regardless of use feature.

  If your code isn't alive, it's dead, jim.

  =item much less memory

  Just using all those pragmas together waste <blink>I<< B<776> kilobytes
  >></blink> of precious memory in my perl, for I<every single perl process
  using our code>, which on our machines, is a lot. In comparison, this
  module only uses I<< B<four> >> kilobytes (I even had to write it out so
  it looks like more) of memory on the same platform.

  The money/time/effort/electricity invested in these gigabytes (probably
  petabytes globally!) of wasted memory could easily save 42 trees, and a
  kitten!


pkgId: 5a77cb42752aebbc7f926c5abd1e6834f1f07c19
name: local-perl-libwww-perl
arch: src
version: 5.808
epoch: 0
release: 7
summary: A Perl interface to the World-Wide Web
url: http://search.cpan.org/dist/libwww-perl/
rpm_license: GPL+ or Artistic
rpm_group: Development/Libraries
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: local-perl-libwww-perl-5.808-7.src.rpm
checksum_type: sha
description:
  The libwww-perl collection is a set of Perl modules which provides a
  simple and consistent application programming interface to the
  World-Wide Web.  The main focus of the library is to provide classes
  and functions that allow you to write WWW clients. The library also
  contain modules that are of more general use and even classes that
  help you implement simple HTTP servers.


pkgId: 3bcf0507e3899297dce59823165766103ac2bf2c
name: local-perl-libwww-perl
arch: src
version: 5.814
epoch: 0
release: 2
summary: libwww-perl - The World-Wide Web library for Perl
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: End Point Corporation
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-libwww-perl-5.814-2.src.rpm
checksum_type: sha
description:
  The libwww-perl collection is a set of Perl modules which provides a
  simple and consistent application programming interface (API) to the
  World-Wide Web.  The main focus of the library is to provide classes
  and functions that allow you to write WWW clients. The library also
  contain modules that are of more general use and even classes that
  help you implement simple HTTP servers.

  Most modules in this library provide an object oriented API.  The user
  agent, requests sent and responses received from the WWW server are
  all represented by objects.  This makes a simple and powerful
  interface to these services.  The interface is easy to extend
  and customize for your own needs.

  The main features of the library are:

  =over 3

  =item *

  Contains various reusable components (modules) that can be
  used separately or together.

  =item *

  Provides an object oriented model of HTTP-style communication.  Within
  this framework we currently support access to http, https, gopher, ftp, news,
  file, and mailto resources.

  =item *

  Provides a full object oriented interface or
  a very simple procedural interface.

  =item *

  Supports the basic and digest authorization schemes.

  =item *

  Supports transparent redirect handling.

  =item *

  Supports access through proxy servers.

  =item *

  Provides parser for F<robots.txt> files and a framework for constructing robots.

  =item *

  Supports parsing of HTML forms.

  =item *

  Implements HTTP content negotiation algorithm that can
  be used both in protocol modules and in server scripts (like CGI
  scripts).

  =item *

  Supports HTTP cookies.

  =item *

  Some simple command line clients, for instance C<lwp-request> and C<lwp-download>.

  =back


pkgId: 3dfc314de5270c33124740aa6b16ca9591ef8aac
name: local-perl-namespace-clean
arch: src
version: 0.21
epoch: 0
release: 1
summary: namespace-clean - Keep imports and functions out of your namespace
description: None.
url: http://www.cpan.org
rpm_license: Artistic
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-namespace-clean-0.21-1.src.rpm
checksum_type: sha
rpm_vendor:
  Robert 'phaylon' Sedlacek <rs@474.at>, Florian Ragwitz <rafl@debian.org>, Jesse Luehrs <doy@tozt.net>


pkgId: 778b0ced10cf375de062844763ccd08aa43da0eb
name: local-perl-parent
arch: src
version: 0.225
epoch: 0
release: 1
summary: parent - Establish an ISA relationship with base classes at compile time
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: AND CONTRIBUTORSRafal <>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-parent-0.225-1.src.rpm
checksum_type: sha
description:
  Allows you to both load one or more modules, while setting up inheritance from
  those modules at the same time.  Mostly similar in effect to

      package Baz;
      BEGIN {
          require Foo;
          require Bar;
          push @ISA, qw(Foo Bar);
      }

  By default, every base class needs to live in a file of its own.
  If you want to have a subclass and its parent class in the same file, you
  can tell C<parent> not to load any modules by using the C<-norequire> switch:

    package Foo;
    sub exclaim { "I CAN HAS PERL" }

    package DoesNotLoadFooBar;
    use parent -norequire, 'Foo', 'Bar';
    

  This is equivalent to the following code:

    package Foo;
    sub exclaim { "I CAN HAS PERL" }

    package DoesNotLoadFooBar;
    push @DoesNotLoadFooBar::ISA, 'Foo', 'Bar';

  This is also helpful for the case where a package lives within
  a differently named file:

    package MyHash;
    use Tie::Hash;
    use parent -norequire, 'Tie::StdHash';

  This is equivalent to the following code:

    package MyHash;
    require Tie::Hash;
    push @ISA, 'Tie::StdHash';

  If you want to load a subclass from a file that C<require> would
  not consider an eligible filename (that is, it does not end in
  either C<.pm> or C<.pmc>), use the following code:

    package MySecondPlugin;
    require './plugins/custom.plugin'; # contains Plugin::Custom
    use parent -norequire, 'Plugin::Custom';


pkgId: d2517c97aec84ee3dc2d8de3cd4b4bdbb70c0067
name: rrdtool
arch: src
version: 1.2.23
epoch: 0
release: 1.rf
summary: Round Robin Database Tool to store and display time-series data
url: http://people.ee.ethz.ch/~oetiker/webtools/rrdtool/
rpm_license: GPL
rpm_vendor: Dag Apt Repository, http://dag.wieers.com/apt/
rpm_group: Applications/Databases
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Dag Wieers <dag@wieers.com>
location_href: local-perl-rrdtool-1.2.23-1.rf.src.rpm
checksum_type: sha
description:
  RRD is the Acronym for Round Robin Database. RRD is a system to store and
  display time-series data (i.e. network bandwidth, machine-room temperature,
  server load average). It stores the data in a very compact way that will not
  expand over time, and it presents useful graphs by processing the data to
  enforce a certain data density. It can be used either via simple wrapper
  scripts (from shell or Perl) or via frontends that poll network devices and
  put a friendly user interface on it.


pkgId: 166f07a51afd9a9ad9c034d86343170ff04b8207
name: local-perl-strictures
arch: src
version: 1.002002
epoch: 0
release: 1
summary: strictures - turn on strict and make all warnings fatal
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: S Trout cpanMSTROUT <mst@shadowcat.co.uk>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-strictures-1.002002-1.src.rpm
checksum_type: sha
description:
  I've been writing the equivalent of this module at the top of my code for
  about a year now. I figured it was time to make it shorter.

  Things like the importer in 'use Moose' don't help me because they turn
  warnings on but don't make them fatal - which from my point of view is
  useless because I want an exception to tell me my code isn't warnings clean.

  Any time I see a warning from my code, that indicates a mistake.

  Any time my code encounters a mistake, I want a crash - not spew to STDERR
  and then unknown (and probably undesired) subsequent behaviour.

  I also want to ensure that obvious coding mistakes, like indirect object
  syntax (and not so obvious mistakes that cause things to accidentally compile
  as such) get caught, but not at the cost of an XS dependency and not at the
  cost of blowing things up on another machine.

  Therefore, strictures turns on indirect checking only when it thinks it's
  running in a compilation (or pod coverage) test - though if this causes
  undesired behaviour this can be overridden by setting the
  PERL_STRICTURES_EXTRA environment variable.

  If additional useful author side checks come to mind, I'll add them to the
  _EXTRA code path only - this will result in a minor version increase (i.e.
  1.000000 to 1.001000 (1.1.0) or similar). Any fixes only to the mechanism of
  this code will result in a subversion increas (i.e. 1.000000 to 1.000001
  (1.0.1)).

  If the behaviour of 'use strictures' in normal mode changes in any way, that
  will constitute a major version increase - and the code already checks
  when its version is tested to ensure that

    use strictures 1;

  will continue to only introduce the current set of strictures even if 2.0 is
  installed.


pkgId: a7d3df9da71a0a8ffde2dbbd7ab6b206f1800c4c
name: local-perl-strictures
arch: src
version: 1.004004
epoch: 0
release: 1
summary: strictures - turn on strict and make all warnings fatal
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: S Trout cpanMSTROUT <mst@shadowcat.co.uk>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: local-perl-strictures-1.004004-1.src.rpm
checksum_type: sha
description:
  I've been writing the equivalent of this module at the top of my code for
  about a year now. I figured it was time to make it shorter.

  Things like the importer in C<use Moose> don't help me because they turn
  warnings on but don't make them fatal -- which from my point of view is
  useless because I want an exception to tell me my code isn't warnings-clean.

  Any time I see a warning from my code, that indicates a mistake.

  Any time my code encounters a mistake, I want a crash -- not spew to STDERR
  and then unknown (and probably undesired) subsequent behaviour.

  I also want to ensure that obvious coding mistakes, like indirect object
  syntax (and not so obvious mistakes that cause things to accidentally compile
  as such) get caught, but not at the cost of an XS dependency and not at the
  cost of blowing things up on another machine.

  Therefore, L<strictures> turns on additional checking, but only when it thinks
  it's running in a test file in a VCS checkout -- although if this causes
  undesired behaviour this can be overridden by setting the
  C<PERL_STRICTURES_EXTRA> environment variable.

  If additional useful author side checks come to mind, I'll add them to the
  C<PERL_STRICTURES_EXTRA> code path only -- this will result in a minor version increase (e.g.
  1.000000 to 1.001000 (1.1.0) or similar). Any fixes only to the mechanism of
  this code will result in a sub-version increase (e.g. 1.000000 to 1.000001
  (1.0.1)).

  If the behaviour of C<use strictures> in normal mode changes in any way, that
  will constitute a major version increase -- and the code already checks
  when its version is tested to ensure that

    use strictures 1;

  will continue to only introduce the current set of strictures even if 2.0 is
  installed.


pkgId: 5668ebfc3ce5f52add6e53dc4675c5c03aed49f4
name: logcheck
arch: src
version: 1.3.14
epoch: 0
release: 1.ep
summary: Analyzes log files and sends noticeable events as email
url: http://logcheck.org/
rpm_license: GPLv2
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/System
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: logcheck-1.3.14-1.ep.src.rpm
checksum_type: sha
description:
  Logcheck is a simple utility which is designed to allow a system administrator
  to view the log-files which are produced upon hosts under their control.

  It does this by mailing summaries of the log-files to them, after first
  filtering out "normal" entries.

  Normal entries are entries which match one of the many included regular
  expression files contain in the database.


pkgId: f25ac48956df96e9f2bf6d2ab4aeedc228f59d4a
name: lua
arch: src
version: 5.1.4
epoch: 0
release: 1
summary: Powerful light-weight programming language
url: http://www.lua.org/
rpm_license: MIT
rpm_vendor: End Point Corporation
rpm_group: Development/Languages
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: lua-5.1.4-1.src.rpm
checksum_type: sha
description:
  Lua is a powerful light-weight programming language designed for
  extending applications. Lua is also frequently used as a
  general-purpose, stand-alone language. Lua is free software.
  Lua combines simple procedural syntax with powerful data description
  constructs based on associative arrays and extensible semantics. Lua
  is dynamically typed, interpreted from bytecodes, and has automatic
  memory management with garbage collection, making it ideal for
  configuration, scripting, and rapid prototyping.


pkgId: 56e93940db716e3fe2b8289e91e6987a294ac516
name: maatkit
arch: src
version: 7332
epoch: 0
release: 2.ep
summary: Essential command-line utilities for MySQL
url: http://www.maatkit.org/
rpm_license: GPLv2 or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/Databases
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: maatkit-7332-2.ep.src.rpm
checksum_type: sha
description:
  This toolkit contains essential command-line utilities for MySQL, such as a
  table checksum tool and query profiler. It provides missing features such as
  checking slaves for data consistency, with emphasis on quality and
  scriptability.


pkgId: c3b7761956aa5f600f6f1279589ed033112927aa
name: memcached
arch: src
version: 1.4.1
epoch: 0
release: 1.ep
summary: High Performance, Distributed Memory Object Cache
url: http://www.danga.com/memcached/
rpm_license: BSD
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: System Environment/Daemons
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: memcached-1.4.1-1.ep.src.rpm
checksum_type: sha
description:
  memcached is a high-performance, distributed memory object caching
  system, generic in nature, but intended for use in speeding up dynamic
  web applications by alleviating database load.


pkgId: 7c57688917c1973c17043e6a441f2e48a75cf496
name: mercurial
arch: src
version: 1.3.1
epoch: 0
release: 3.ep
summary: A fast, lightweight distributed source control management system
url: http://www.selenic.com/mercurial/
rpm_license: GPLv2
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Tools
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: mercurial-1.3.1-3.ep.src.rpm
checksum_type: sha
description:
  Mercurial is a fast, lightweight source control management system designed
  for efficient handling of very large distributed projects.

  Quick start: http://www.selenic.com/mercurial/wiki/index.cgi/QuickStart
  Tutorial: http://www.selenic.com/mercurial/wiki/index.cgi/Tutorial
  Extensions: http://www.selenic.com/mercurial/wiki/index.cgi/CategoryExtension


pkgId: 3b02f6dc9f7ad6f59e28dc2defda9adf28224635
name: mhash
arch: src
version: 0.9.2
epoch: 0
release: 6%{dist}
summary: Thread-safe hash algorithms library
url: http://mhash.sourceforge.net/
rpm_license: LGPL
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: System Environment/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: mhash-0.9.2-6%{dist}.src.rpm
checksum_type: sha
description:
  Mhash is a free library which provides a uniform interface to a
  large number of hash algorithms.

  These algorithms can be used to compute checksums, message digests,
  and other signatures. The HMAC support implements the basics for
  message authentication, following RFC 2104. In the later versions
  some key generation algorithms, which use hash algorithms, have been
  added. Currently, the library supports the algorithms: SHA1, GOST,
  HAVAL256, HAVAL224, HAVAL192, HAVAL160, HAVAL128, MD5, MD4, MD2,
  RIPEMD128/160/256/320, TIGER, TIGER160, TIGER128, SHA224/384/512,
  Whirlpool, SNEFRU128/256, CRC32B and CRC32 checksums.


pkgId: bfde8e794170bb2a53239aa22bfcd2530ce3f576
name: mod_geoip
arch: src
version: 1.2.5
epoch: 0
release: 4.ep
summary: GeoIP module for the Apache HTTP Server
url: http://www.maxmind.com/app/mod_geoip
rpm_license: ASL 1.1
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: System Environment/Daemons
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: mod_geoip-1.2.5-4.ep.src.rpm
checksum_type: sha
description:
  mod_geoip is an Apache module for finding the country that a web request
  originated from.  It uses the GeoIP library and database to perform
  the lookup.  It is free software, licensed under the Apache license.


pkgId: 7c85752ebccacc48f3acedd27fcc246fe0ad8754
name: mrsync
arch: src
version: 4.0.0
epoch: 0
release: 1
summary: Transfers files to multiple targets simultaneously
url: http://sourceforge.net/projects/mrsync/
rpm_license: GPL
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: File tools
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Jon Jensen <jon@endpoint.com>
location_href: mrsync-4.0.0-1.src.rpm
checksum_type: sha
description:
  mrsync is a tool to transfer files from a master to many target LAN
  machines using Unix socket's multicast. It dynamically adjusts its speed
  of transfering to go easy on the network and to leave no one behind.
  Benchmarked at 4 hours for 140 GB to 100 targets over 1 Gbps LAN.


pkgId: 40066e22ac7215fae31864406b1ca88a0ffc38d1
name: msttcorefonts
arch: src
version: 1.3
epoch: 0
release: 5
summary: TrueType core fonts for the web
rpm_license: Spec file is GPL, binary RPM is gratis but non-distributable
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: User Interface/X
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Daniel Resare <corefonts@resare.com>
location_href: msttcorefonts-1.3-5.src.rpm
checksum_type: sha
description:
  The TrueType core fonts for the web that was once available from
  http://www.microsoft.com/typography/fontpack/. The src rpm is cleverly
  constructed so that the actual fonts are downloaded from Sourceforge's site
  at build time. Therefore this package technically does not 'redistribute'
  the fonts, it just makes it easy to install them on a linux system.


pkgId: 0f0c6148c3018292467c05895532020e28bd3114
name: munin
arch: src
version: 1.2.6
epoch: 0
release: 4.ep
summary: Network-wide graphing framework (grapher/gatherer)
url: http://munin.projects.linpro.no/
rpm_license: GPLv2 and Bitstream Vera
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: System Environment/Daemons
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: munin-1.2.6-4.ep.src.rpm
checksum_type: sha
description:
  Munin is a highly flexible and powerful solution used to create graphs of
  virtually everything imaginable throughout your network, while still
  maintaining a rattling ease of installation and configuration.

  This package contains the grapher/gatherer. You will only need one instance of
  it in your network. It will periodically poll all the nodes in your network
  it's aware of for data, which it in turn will use to create graphs and HTML
  pages, suitable for viewing with your graphical web browser of choice.

  Munin is written in Perl, and relies heavily on Tobi Oetiker's excellent
  RRDtool.


pkgId: 4dc399b9afb6c3f37926a7d739d0dba5e92a7a4c
name: nagcon
arch: src
version: 0.0.30
epoch: 0
release: 1
url: http://www.vanheusden.com/nagcon
rpm_license: GPL
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/Internet
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Corporation <hosting@endpoint.com>
location_href: nagcon-0.0.30-1.src.rpm
checksum_type: sha
summary:
  a console application interfacing to Nagios which gives you an overview of all hosts with troubled services.

description:
  Nagcon is a console application interfacing to Nagios which gives you an overview of all hosts with troubled services.


pkgId: 7ed4b47016d2daf0007bbce90630be643c6f0994
name: nagios
arch: src
version: 3.0.3
epoch: 0
release: 6
summary: Host/service/network monitoring program
url: http://www.nagios.org/
rpm_license: GPLv2+
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/System
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: nagios-3.0.3-6.src.rpm
checksum_type: sha
description:
  Nagios is a program that will monitor hosts and services on your
  network.  It has the ability to send email or page alerts when a
  problem arises and when a problem is resolved.  Nagios is written
  in C and is designed to run under Linux (and some other *NIX
  variants) as a background process, intermittently running checks
  on various services that you specify.

  The actual service checks are performed by separate "plugin" programs
  which return the status of the checks to Nagios. The plugins are
  available at http://sourceforge.net/projects/nagiosplug.

  This package provides the core program, web interface, and documentation
  files for Nagios. Development files are built as a separate package.


pkgId: f9b16558ba43ddf426ef92e5ac22366194724213
name: nagios-of-plugins
arch: src
version: 0.10.1
epoch: 0
release: 1.ep
summary: Additional Nagios plugins by Open Fusion
url: http://www.openfusion.com.au/labs/nagios/
rpm_license: GPL
rpm_vendor: Open Fusion, http://www.openfusion.com.au
rpm_group: Applications/System
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Gavin Carr <gavin@openfusion.com.au>
location_href: nagios-of-plugins-0.10.1-1.ep.src.rpm
checksum_type: sha
description:
  This package contains additional plugins for the Nagios monitoring system,
  written by Gavin Carr of Open Fusion. It requires Nagios::Plugin from CPAN.

  - check_daemontools_service
  - check_db_query_rowcount
  - check_file
  - check_grep
  - check_inodes
  - check_ipmi_sdr
  - check_kernel_version
  - check_linux_raid
  - check_memory
  - check_mountpoint
  - check_newest_file
  - check_pcap_traffic
  - check_qmailq
  - check_tcp_range
  - check_yum

  See the relevant plugin's -h output for usage details.


pkgId: 7cb991246f0f93a4b40d997c4e9c36cb7cda546d
name: nagios-of-plugins
arch: src
version: 0.9.5
epoch: 0
release: 2.ep
summary: Additional Nagios plugins by Open Fusion
url: http://www.openfusion.com.au/labs/nagios/
rpm_license: GPL
rpm_vendor: Open Fusion, http://www.openfusion.com.au
rpm_group: Applications/System
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Gavin Carr <gavin@openfusion.com.au>
location_href: nagios-of-plugins-0.9.5-2.ep.src.rpm
checksum_type: sha
description:
  This package contains additional plugins for the Nagios monitoring system,
  written by Gavin Carr of Open Fusion. It requires Nagios::Plugin from CPAN.

  - check_daemontools_service
  - check_db_query_rowcount
  - check_file
  - check_grep
  - check_inodes
  - check_ipmi_sdr
  - check_kernel_version
  - check_linux_raid
  - check_memory
  - check_qmailq
  - check_tcp_range
  - check_up2date
  - check_yum

  See the relevant plugin's -h output for usage details.


pkgId: 6553a333b80161705270512d060f7336b5eb618d
name: nagios-plugin-mysql_health
arch: src
version: 2.1.1
epoch: 0
release: 1
summary: Nagios plugin: monitor various performance-related characteristics of a MySQL DB
url: http://labs.consol.de/lang/de/nagios/check_mysql_health/
rpm_license: GPL v2+
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Networking
rpm_buildhost: rhel5-build32
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: nagios-plugin-mysql_health-2.1.1-1.src.rpm
checksum_type: sha
description:
  Nagios plugin which allows you to monitor various performance-related
  characteristics of a MySQL database.


pkgId: 82089c38756826640b192d523d1f249a1dfe4fda
name: nagios-plugins
arch: src
version: 1.4.12
epoch: 0
release: 2
summary: Host/service/network monitoring program plugins for Nagios
url: http://nagiosplug.sourceforge.net/
rpm_license: GPL
rpm_vendor: End Point Corporation
rpm_group: Applications/System
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Dag Wieers <dag@wieers.com>
location_href: nagios-plugins-1.4.12-2.src.rpm
checksum_type: sha
description:
  This package contains the basic plugins necessary for use with the
  Nagios package. This package should install cleanly on almost any
  RPM-based system.

  But you may need additional packages. Depending on what plugins you
  use, the following packages may be required:

      bind-utils, mysql, net-snmp-utils, ntp, openldap,
      openssh-clients, openssl, postgresql-libs
      qstat, radiusclient, samba-client, sendmail


pkgId: c1500b30538c919a85a6a1545d1962797627fa8e
name: nagios-plugins
arch: src
version: 1.4.14
epoch: 0
release: 4.ep.1
summary: Host/service/network monitoring program plugins for Nagios
url: http://nagiosplug.sourceforge.net/
rpm_license: GPLv2+
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/System
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: nagios-plugins-1.4.14-4.ep.1.src.rpm
checksum_type: sha
description:
  Nagios is a program that will monitor hosts and services on your
  network, and to email or page you when a problem arises or is
  resolved. Nagios runs on a Unix server as a background or daemon
  process, intermittently running checks on various services that you
  specify. The actual service checks are performed by separate "plugin"
  programs which return the status of the checks to Nagios. This package
  contains those plugins.


pkgId: 1a8133b18e2f11f6a350b88c8317ee99a254e8a4
name: nethogs
arch: src
version: 0.7
epoch: 0
release: 4.20080627cvs.ep
summary: A tool resembling top for network traffic
url: http://nethogs.sourceforge.net
rpm_license: GPL+
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/Internet
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: nethogs-0.7-4.20080627cvs.ep.src.rpm
checksum_type: sha
description:
  NetHogs is a small "net top" tool.

  Instead of breaking the traffic down per protocol or per subnet, like
  most such tools do, it groups bandwidth by process and does not rely
  on a special kernel module to be loaded.

  So if there's suddenly a lot of network traffic, you can fire up
  NetHogs and immediately see which PID is causing this, and if it's
  some kind of spinning process, kill it.


pkgId: 236d5cca9fb7f8ef7e73e1db221ad85f5e8ec201
name: nginx
arch: src
version: 0.6.32
epoch: 0
release: 2
summary: Robust, small and high performance http and reverse proxy server
url: http://nginx.net/
rpm_license: BSD
rpm_vendor: End Point Corporation
rpm_group: System Environment/Daemons
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: nginx-0.6.32-2.src.rpm
checksum_type: sha
description:
  Nginx [engine x] is an HTTP(S) server, HTTP(S) reverse proxy and IMAP/POP3
  proxy server written by Igor Sysoev.

  One third party module, nginx-upstream-fair, is added


pkgId: 8d350aa52c1ccbd0d864445e0e15f03e159f4c40
name: nginx
arch: src
version: 0.7.64
epoch: 0
release: 2.ep
summary: Robust, small and high performance http and reverse proxy server
url: http://nginx.net/
rpm_license: BSD
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: System Environment/Daemons
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: nginx-0.7.64-2.ep.src.rpm
checksum_type: sha
description:
  Nginx [engine x] is an HTTP(S) server, HTTP(S) reverse proxy and IMAP/POP3
  proxy server written by Igor Sysoev.


pkgId: e1b125c3ec340882447733c5ae04059f550a8062
name: nrpe
arch: src
version: 2.12
epoch: 0
release: 1.ep
summary: Host/service/network monitoring agent for Nagios
url: http://www.nagios.org
rpm_license: GPLv2
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/System
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: nrpe-2.12-1.ep.src.rpm
checksum_type: sha
description:
  Nrpe is a system daemon that will execute various Nagios plugins
  locally on behalf of a remote (monitoring) host that uses the
  check_nrpe plugin.  Various plugins that can be executed by the
  daemon are available at:
  http://sourceforge.net/projects/nagiosplug

  This package provides the core agent.


pkgId: ab82625cd971d15b5d1ed765e81f577ed9d999e2
name: oidentd
arch: src
version: 2.0.8
epoch: 0
release: 5
summary: Implementation of the RFC1413 identification server
url: http://ojnk.sourceforge.net/
rpm_license: GPLv2
rpm_vendor: End Point Corporation
rpm_group: System Environment/Daemons
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: oidentd-2.0.8-5.src.rpm
checksum_type: sha
description:
  The oidentd package contains identd, which implements the RFC1413
  identification server.  Identd looks up specific TCP/IP connections
  and returns either the user name or other information about the
  process that owns the connection.

  Install oidentd if you need to look up information about specific
  TCP/IP connections.


pkgId: d820f766be7fa098149c2b90d14cc82abf7e360c
name: p7zip
arch: src
version: 4.58
epoch: 0
release: 1
summary: Very high compression ratio file archiver
url: http://p7zip.sourceforge.net/
rpm_license: LGPLv2 and (LGPLv2+ or CPL)
rpm_vendor: End Point Corporation
rpm_group: Applications/Archiving
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: p7zip-4.58-1.src.rpm
checksum_type: sha
description:
  p7zip is a port of 7za.exe for Unix. 7-Zip is a file archiver with a very high
  compression ratio. The original version can be found at http://www.7-zip.org/.


pkgId: abb07e517f3bf82c81aacc0f4a878f57b12c3e0f
name: pacemaker
arch: src
version: 1.0.7
epoch: 0
release: 4.ep
summary: Scalable High-Availability cluster resource manager
url: http://www.clusterlabs.org
rpm_license: GPLv2+ and LGPLv2+
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: System Environment/Daemons
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: pacemaker-1.0.7-4.ep.src.rpm
checksum_type: sha
description:
  Pacemaker is an advanced, scalable High-Availability cluster resource
  manager for Linux-HA (Heartbeat) and/or OpenAIS.

  It supports "n-node" clusters with significant capabilities for
  managing resources and dependencies.

  It will run scripts at initialization, when machines go up or down,
  when related resources fail and can be configured to periodically check
  resource health.

  Available rpmbuild rebuild options:
    --without : heartbeat ais


pkgId: 9e2a5d53fa01075c668c71990983103ffc3cb5f0
name: pbzip2
arch: src
version: 1.0.2
epoch: 0
release: 4
summary: Parallel implementation of bzip2
url: http://www.compression.ca/pbzip2/
rpm_license: BSD
rpm_vendor: End Point Corporation
rpm_group: Applications/File
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: pbzip2-1.0.2-4.src.rpm
checksum_type: sha
description:
  PBZIP2 is a parallel implementation of the bzip2 block-sorting file
  compressor that uses pthreads and achieves near-linear speedup on SMP
  machines.  The output of this version is fully compatible with bzip2
  v1.0.2 or newer (ie: anything compressed with pbzip2 can be
  decompressed with bzip2).


pkgId: 689d369b46f094e25584e7c60a1941f46074905f
name: pdftk
arch: src
version: 1.41
epoch: 0
release: 1.rf
summary: PDF Tool Kit
url: http://www.pdfhacks.com/pdftk/
rpm_license: GPL
rpm_vendor: Dag Apt Repository, http://dag.wieers.com/apt/
rpm_group: Applications/Publishing
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Dag Wieers <dag@wieers.com>
location_href: pdftk-1.41-1.rf.src.rpm
checksum_type: sha
description:
  If PDF is electronic paper, then pdftk is an electronic staple-remover,
  hole-punch, binder, secret-decoder-ring, and X-Ray-glasses. Pdftk is a simple
  tool for doing everyday things with PDF documents. Keep one in the top drawer
  of your desktop and use it to:

      * Merge PDF Documents
      * Split PDF Pages into a New Document
      * Decrypt Input as Necessary (Password Required)
      * Encrypt Output as Desired
      * Burst a PDF Document into Single Pages
      * Report on PDF Metrics, including Metadata and Bookmarks
      * Uncompress and Re-Compress Page Streams
      * Repair Corrupted PDF (Where Possible)


pkgId: 69fabf3794f175ac071d17671bf37b5841a8a0a8
name: pdftk
arch: src
version: 2.02
epoch: 0
release: 1.ep
summary: PDFtk, The PDF Toolkit
url: http://www.pdftk.com
rpm_license: GPL
rpm_vendor: Steward and Lee, LLC, http://www.pdflabs.com
rpm_group: Applications/Publishing
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Sid Steward
location_href: pdftk-2.02-1.ep.src.rpm
checksum_type: sha
description:
  If PDF is electronic paper, then pdftk is an electronic staple-remover,
  hole-punch, binder, secret-decoder-ring, and X-Ray-glasses. Pdftk is a simple
  tool for doing everyday things with PDF documents. Use it to:

     * Merge PDF Documents or Collate PDF Page Scans
     * Split PDF Pages into a New Document
     * Rotate PDF Documents or Pages
     * Decrypt Input as Necessary (Password Required)
     * Encrypt Output as Desired
     * Fill PDF Forms with X/FDF Data and/or Flatten Forms
     * Generate FDF Data Stencils from PDF Forms
     * Apply a Background Watermark or a Foreground Stamp
     * Report PDF Metrics, Bookmarks and Metadata
     * Add/Update PDF Bookmarks or Metadata
     * Attach Files to PDF Pages or the PDF Document
     * Unpack PDF Attachments
     * Burst a PDF Document into Single Pages
     * Uncompress and Re-Compress Page Streams
     * Repair Corrupted PDF (Where Possible)


pkgId: 115955d9b4792bf102d4eb0ef2a1a248e005c598
name: perl-Config-General
arch: src
version: 2.38
epoch: 0
release: 0.1.ep
summary: Generic configuration module for Perl
url: http://search.cpan.org/dist/Config-General/
rpm_license: GPL+ or Artistic
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: perl-Config-General-2.38-0.1.ep.src.rpm
checksum_type: sha
description:
  This module opens a config file and parses it's contents for
  you. After parsing the module returns a hash structure which contains
  the representation of the config file.
  The format of config files supported by Config::General is inspired by
  the well known apache config format, in fact, this module is 100%
  read-compatible to apache configs, but you can also just use simple
  name/value pairs in your config files.
  In addition to the capabilities of a apache config file it supports
  some enhancements such as here-documents, C- style comments or
  multiline options. It is also possible to save the config back to
  disk, which makes the module a perfect backend for configuration
  interfaces.
  It is possible to use variables in config files and there exists also
  support for object oriented access to the configuration.


pkgId: e74325135e4ddf2ea963df3e25ceba6f0c24e31e
name: perl-Error
arch: src
version: 0.17014
epoch: 0
release: 1.rf
summary: Error/exception handling in an OO-ish way
url: http://search.cpan.org/dist/Error/
rpm_license: Artistic/GPL
rpm_vendor: Dag Apt Repository, http://dag.wieers.com/apt/
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Dag Wieers <dag@wieers.com>
location_href: perl-Error-0.17014-1.rf.src.rpm
checksum_type: sha
description:
  The Error package provides two interfaces. Firstly Error provides a procedural
  interface to exception handling. Secondly Error is a base class for
  errors/exceptions that can either be thrown, for subsequent catch, or can
  simply be recorded.


pkgId: c756dcdef7f5faf1934f76c519089b9e28be7847
name: perl-GSSAPI
arch: src
version: 0.26
epoch: 0
release: 1
summary: GSSAPI - Perl extension providing access to the GSSAPIv2 library
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: byAchim Grolms <perl@grolmsnet.de>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: perl-GSSAPI-0.26-1.src.rpm
checksum_type: sha
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: c6ce787a3755c3ef69cd00bc093c46993e233c08
name: perl-Math-Calc-Units
arch: src
version: 1.06
epoch: 0
release: 1
summary: Math-Calc-Units - Human-readable unit-aware calculator
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Steve Fink <sfink@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: perl-Math-Calc-Units-1.06-1.src.rpm
checksum_type: sha
description:
  C<Math::Calc::Units> is a simple calculator that keeps track of units. It
  currently handles combinations of byte sizes and duration only,
  although adding any other multiplicative types is easy. Any unknown
  type is treated as a unique user type (with some effort to map English
  plurals to their singular forms).

  The primary intended use is via the C<ucalc> script that prints out
  all of the "readable" variants of a value. For example, C<"3 bytes">
  will only produce C<"3 byte">, but C<"3 byte / sec"> produces the
  original along with C<"180 byte / minute">, C<"10.55 kilobyte / hour">,
  etc.

  The C<Math::Calc::Units> interface only provides for string-based
  computations, which could result in a large loss of precision for some
  applications. If you need the exact result, you may pass in an extra
  parameter C<'exact'> to C<calc> or C<convert>, causing them to return a
  2-element list containing the numerical result and a string describing
  the units of that result:

      my ($value, $units) = convert("10MB/sec", "GB/day");

  (In scalar context, they just return the numeric value.)


pkgId: 50cc75016d7fd7f0157c21bf7ccd2df19c0480ec
name: perl-Nagios-Plugin
arch: src
version: 0.31
epoch: 0
release: 1
summary: Nagios-Plugin - A family of perl modules to streamline writing Nagios
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Nagios Plugin Development Team <nagiosplug-devel@lists.sourceforge.net>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: perl-Nagios-Plugin-0.31-1.src.rpm
checksum_type: sha
description:
  Nagios::Plugin and its associated Nagios::Plugin::* modules are a
  family of perl modules to streamline writing Nagios plugins. The main
  end user modules are Nagios::Plugin, providing an object-oriented
  interface to the entire Nagios::Plugin::* collection, and
  Nagios::Plugin::Functions, providing a simpler functional interface to
  a useful subset of the available functionality.

  The purpose of the collection is to make it as simple as possible for
  developers to create plugins that conform the Nagios Plugin guidelines
  (http://nagiosplug.sourceforge.net/developer-guidelines.html).


pkgId: 342223a4f922b05e511f6d073fdeed8d03305bf2
name: perl-Net-SMTP-SSL
arch: src
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: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: perl-Net-SMTP-SSL-1.01-1.src.rpm
checksum_type: sha
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: 755470e50dfcd07f2c8a9acb7e017d7e8d4b1b09
name: perl-Pod-Escapes
arch: src
version: 1.04
epoch: 0
release: 1
summary: Pod-Escapes - - for resolving Pod EE<lt>...E<gt> sequences
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sean M Burke <Csburke@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: perl-Pod-Escapes-1.04-1.src.rpm
checksum_type: sha
description:
  This module provides things that are useful in decoding
  Pod EE<lt>...E<gt> sequences.  Presumably, it should be used
  only by Pod parsers and/or formatters.

  By default, Pod::Escapes exports none of its symbols.  But
  you can request any of them to be exported.
  Either request them individually, as with
  C<use Pod::Escapes qw(symbolname symbolname2...);>,
  or you can do C<use Pod::Escapes qw(:ALL);> to get all
  exportable symbols.


pkgId: bcbeadff0ef9dee03fcc6aa8f931d8387d973430
name: perl-Pod-Simple
arch: src
version: 3.07
epoch: 0
release: 1
summary: Pod-Simple - framework for parsing Pod
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Sean M Burke <Csburke@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: perl-Pod-Simple-3.07-1.src.rpm
checksum_type: sha
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. The Pod format is explained
  in the L<perlpod|perlpod> man page; the most common formatter is called
  "perldoc".

  Pod formatters can use Pod::Simple to parse Pod documents into produce
  renderings of them in plain ASCII, in HTML, or in any number of other
  formats. Typically, such formatters will be subclasses of Pod::Simple,
  and so they will inherit its methods, like C<parse_file>.

  If you're reading this document just because you have a Pod-processing
  subclass that you want to use, this document (plus the documentation for
  the subclass) is probably all you'll need to read.

  If you're reading this document because you want to write a formatter
  subclass, continue reading this document, and then read
  L<Pod::Simple::Subclassing>, and then possibly even read L<perlpodspec>
  (some of which is for parser-writers, but much of which is notes to
  formatter-writers).


pkgId: 61c03d46176911054168e5f69371ceee5fd8c803
name: perl-TermReadKey
arch: src
version: 2.30
epoch: 0
release: 1
summary: TermReadKey - A perl module for simple terminal control
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Kenneth Albanowski <kjahds@kjahds.com>
rpm_group: Applications/CPAN
rpm_buildhost: rhel5-build32
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: perl-TermReadKey-2.30-1.src.rpm
checksum_type: sha
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.

  =over 8

  =item ReadMode MODE [, Filehandle]

  Takes an integer argument, which can currently be one of the following
  values:

      0    Restore original settings.
      1    Change to cooked mode.
      2	 Change to cooked mode with echo off.
            (Good for passwords)
      3    Change to cbreak mode.
      4    Change to raw mode.
      5    Change to ultra-raw mode.
            (LF to CR/LF translation turned off)

      Or, you may use the synonyms:

      restore
      normal
      noecho
      cbreak
      raw
      ultra-raw

  These functions are automatically applied to the STDIN handle if no
  other handle is supplied. Modes 0 and 5 have some special properties
  worth mentioning: not only will mode 0 restore original settings, but it
  cause the next ReadMode call to save a new set of default settings. Mode
  5 is similar to mode 4, except no CR/LF translation is performed, and if
  possible, parity will be disabled (only if not being used by the terminal,
  however. It is no different from mode 4 under Windows.)

  If you are executing another program that may be changing the terminal mode,
  you will either want to say

      ReadMode 1
      system('someprogram');
      ReadMode 1;

  which resets the settings after the program has run, or:

      $somemode=1;
      ReadMode 0;
      system('someprogram');
      ReadMode 1;

  which records any changes the program may have made, before resetting the
  mode.

  =item ReadKey MODE [, Filehandle]

  Takes an integer argument, which can currently be one of the following
  values:

      0    Perform a normal read using getc
      -1   Perform a non-blocked read
      >0	 Perform a timed read

  (If the filehandle is not supplied, it will default to STDIN.) If there is
  nothing waiting in the buffer during a non-blocked read, then undef will be
  returned. Note that if the OS does not provide any known mechanism for
  non-blocking reads, then a C<ReadKey -1> can die with a fatal error. This
  will hopefully not be common.

  If MODE is greater then zero, then ReadKey will use it as a timeout value in
  seconds (fractional seconds are allowed), and won't return C<undef> until
  that time expires. (Note, again, that some OS's may not support this timeout
  behaviour.) If MODE is less then zero, then this is treated as a timeout
  of zero, and thus will return immediately if no character is waiting. A MODE
  of zero, however, will act like a normal getc.

  There are currently some limitations with this call under Windows. It may be
  possible that non-blocking reads will fail when reading repeating keys from
  more then one console.

  =item ReadLine MODE [, Filehandle]

  Takes an integer argument, which can currently be one of the following
  values:

      0    Perform a normal read using scalar(<FileHandle>)
      -1   Perform a non-blocked read
      >0	 Perform a timed read

  If there is nothing waiting in the buffer during a non-blocked read, then
  undef will be returned. Note that if the OS does not provide any known
  mechanism for non-blocking reads, then a C<ReadLine 1> can die with a fatal
  error. This will hopefully not be common. Note that a non-blocking test is
  only performed for the first character in the line, not the entire line.
  This call will probably B<not> do what you assume, especially with
  ReadMode's higher then 1. For example, pressing Space and then Backspace
  would appear to leave you where you started, but any timeouts would now
  be suspended.

  This call is currently not available under Windows.

  =item GetTerminalSize [Filehandle]

  Returns either an empty array if this operation is unsupported, or a four
  element array containing: the width of the terminal in characters, the
  height of the terminal in character, the width in pixels, and the height in
  pixels. (The pixel size will only be valid in some environments.)

  Under Windows, this function must be called with an "output" filehandle,
  such as STDOUT, or a handle opened to CONOUT$.

  =item SetTerminalSize WIDTH,HEIGHT,XPIX,YPIX [, Filehandle]

  Return -1 on failure, 0 otherwise. Note that this terminal size is only for
  B<informative> value, and changing the size via this mechanism will B<not>
  change the size of the screen. For example, XTerm uses a call like this when
  it resizes the screen. If any of the new measurements vary from the old, the
  OS will probably send a SIGWINCH signal to anything reading that tty or pty.

  This call does not work under Windows.

  =item GetSpeeds [, Filehandle]

  Returns either an empty array if the operation is unsupported, or a two
  value array containing the terminal in and out speeds, in B<decimal>. E.g,
  an in speed of 9600 baud and an out speed of 4800 baud would be returned as
  (9600,4800). Note that currently the in and out speeds will always be
  identical in some OS's. No speeds are reported under Windows.

  =item GetControlChars [, Filehandle]

  Returns an array containing key/value pairs suitable for a hash. The pairs
  consist of a key, the name of the control character/signal, and the value
  of that character, as a single character. This call does nothing under Windows.

  Each key will be an entry from the following list:

  	DISCARD
  	DSUSPEND
  	EOF
  	EOL
  	EOL2
  	ERASE
  	ERASEWORD
  	INTERRUPT
  	KILL
  	MIN
  	QUIT
  	QUOTENEXT
  	REPRINT
  	START
  	STATUS
  	STOP
  	SUSPEND
  	SWITCH
  	TIME

  Thus, the following will always return the current interrupt character,
  regardless of platform.

  	%keys = GetControlChars;
  	$int = $keys{INTERRUPT};

  =item SetControlChars [, Filehandle]

  Takes an array containing key/value pairs, as a hash will produce. The pairs
  should consist of a key that is the name of a legal control
  character/signal, and the value should be either a single character, or a
  number in the range 0-255. SetControlChars will die with a runtime error if
  an invalid character name is passed or there is an error changing the
  settings. The list of valid names is easily available via

  	%cchars = GetControlChars();
  	@cnames = keys %cchars;

  This call does nothing under Windows.

  =back


pkgId: e9c0b33eac10817576a76536bb0521296f11883a
name: perl-cpan2rpm
arch: src
version: 2.028
epoch: 0
release: 1
summary: cpan2rpm - A Perl module packager
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Erick Calder <ecalder@cpan.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: perl-cpan2rpm-2.028-1.src.rpm
checksum_type: sha
description:
  This script generates an RPM package from a Perl module.  It uses the standard RPM file structure and creates a spec file, a source RPM, and a binary, leaving these in their respective directories.

  The script can operate on local files, directories, urls and CPAN module names.  Install this package if you want to create RPMs out of Perl modules.

  The syntax for cpan2rpm supports multiple *distribution* names, which can take one of four different forms:

  =over

  =item 1. a CPAN module name (e.g. XML::Simple) - When a module name is passed, the script will "walk" search.cpan.org to determine the latest distribution.  If an exact match is not found, the CPAN module is used to make this determination.  If you have not yet configured this module, please refer to the REQUIREMENTS section below for further instructions.

  =item 2. a URL (both http:// and ftp:// style locators will work) - In this and the above case, an automatic download of the needed tarball is performed (see notes for how).  The tarball is deposited in the SOURCES directory.

  =item 3. a path to a tarball (e.g. /tmp/XML-Simple-1.05.tar.gz) - In this case, the tarball indicated gets copied to the SOURCES directory.

  =item 4. a directory path - The directory specified must contain a Makefile.PL.  If the user intends to build a package from a directory (i.e. user does NOT specify --spec-only), the commands:

      perl Makefile.PL
      make
      make dist

  will be performed in that directory in order to create the tarball necessary for package creation.

  =back


pkgId: d6ef9884d541bde60534fedec0211ca07b476a25
name: perl-enum
arch: src
version: 1.016
epoch: 0
release: 1
summary: enum - C style enumerated types and bitmask flags in Perl
url: http://www.cpan.org
rpm_license: Artistic
rpm_vendor: Zenin <zenin@archive.rhps.org>
rpm_group: Applications/CPAN
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Arix International <cpan2rpm@arix.com>
location_href: perl-enum-1.016-1.src.rpm
checksum_type: sha
description:
  Defines a set of symbolic constants with ordered numeric values ala B<C> B<enum> types.

  Now capable of creating creating ordered bitmask constants as well.  See the B<BITMASKS>
  section for details.

  What are they good for?  Typical uses would be for giving mnemonic names to indexes of
  arrays.  Such arrays might be a list of months, days, or a return value index from
  a function such as localtime():

    use enum qw(
        :Months_=0 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
        :Days_=0   Sun Mon Tue Wed Thu Fri Sat
        :LC_=0     Sec Min Hour MDay Mon Year WDay YDay Isdst
    );

    if ((localtime)[LC_Mon] == Months_Jan) {
        print "It's January!\n";
    }
    if ((localtime)[LC_WDay] == Days_Fri) {
        print "It's Friday!\n";
    }

  This not only reads easier, but can also be typo-checked at compile time when
  run under B<use strict>.  That is, if you misspell B<Days_Fri> as B<Days_Fry>,
  you'll generate a compile error.


pkgId: a054597667db8eeedf4f30d2bc45ba4f6da34692
name: pfqueue
arch: src
version: 0.5.6
epoch: 0
release: 4.ep
summary: Queue manager for the Postfix/Exim Mail Transport Agents
url: http://pfqueue.sourceforge.net/
rpm_license: GPL
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/Internet
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: pfqueue-0.5.6-4.ep.src.rpm
checksum_type: sha
description:
  pfqueue is a console application for managing mail queues used by the Postfix
  or Exim mail transport agents.


pkgId: 41bfba55e2d291aeb24eca584896e64b6ef4907e
name: pg_top
arch: src
version: 3.6.2
epoch: 0
release: 1.ep
summary: 'top' for PostgreSQL process
url: http://pgfoundry.org/projects/ptop
rpm_license: BSD
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/Databases
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: pg_top-3.6.2-1.ep.src.rpm
checksum_type: sha
description:
  pg_top is 'top' for PostgreSQL processes. See running queries,
  query plans, issued locks, and table and index statistics.


pkgId: 6c35a1f71770a6d46b13035bd8612dbfb139d87e
name: php-extras
arch: src
version: 5.1.6
epoch: 0
release: 4
summary: Additional PHP modules from the standard PHP distribution
url: http://www.php.net/
rpm_license: The PHP License
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Languages
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: php-extras-5.1.6-4.src.rpm
checksum_type: sha
description:
  PHP is an HTML-embedded scripting language.

  This package contains various additional modules for PHP, which
  have not been included in the basic PHP package for Fedora Core.


pkgId: 353dda87f4157e0cace206f6874e49856382ebdb
name: php-fpdf
arch: src
version: 1.6
epoch: 0
release: 5.ep
summary: PHP class to generate PDF Files
url: http://www.fpdf.org
rpm_license: MIT
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: php-fpdf-1.6-5.ep.src.rpm
checksum_type: sha
description:
  FPDF is a PHP class which allows to generate PDF files with pure PHP, that is
  to say without using the PDFlib library. F from FPDF stands for Free: you may
  use it for any kind of usage and modify it to suit your needs.


pkgId: 82c7cfeb344b75f88acd2799caa9c44485290c3e
name: php-pear-Auth-SASL
arch: src
version: 1.0.2
epoch: 0
release: 4
summary: PEAR: Abstraction of various SASL mechanism responses
url: http://pear.php.net/package/Auth_SASL
rpm_license: BSD
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: php-pear-Auth-SASL-1.0.2-4.src.rpm
checksum_type: sha
description:
  Provides code to generate responses to common SASL mechanisms, including:
  o Digest-MD5
  o CramMD5
  o Plain
  o Anonymous
  o Login (Pseudo mechanism)


pkgId: 7382c813abe1f215db55ac6379f35c1533d466e6
name: php-pear-DB
arch: src
version: 1.7.13
epoch: 0
release: 1
summary: PEAR: Database Abstraction Layer
url: http://pear.php.net/package/DB
rpm_license: PHP
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: php-pear-DB-1.7.13-1.src.rpm
checksum_type: sha
description:
  DB is a database abstraction layer providing:
  * an OO-style query API
  * portability features that make programs written for one DBMS work with
    other DBMS's
  * a DSN (data source name) format for specifying database servers
  * prepare/execute (bind) emulation for databases that don't support it natively
  * a result object for each query response
  * portable error codes
  * sequence emulation
  * sequential and non-sequential row fetching as well as bulk fetching
  * formats fetched rows as associative arrays, ordered arrays or objects
  * row limit support
  * transactions support
  * table information interface
  * DocBook and phpDocumentor API documentation

  DB layers itself on top of PHP's existing database extensions.


pkgId: 4f431554c165bca47ff44b3c86382d53b3c8b16c
name: php-pear-MDB2
arch: src
version: 2.4.1
epoch: 0
release: 2
summary: Database Abstraction Layer
url: http://pear.php.net/package/MDB2
rpm_license: BSD
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: php-pear-MDB2-2.4.1-2.src.rpm
checksum_type: sha
description:
  PEAR::MDB2 is a merge of the PEAR::DB and Metabase php database abstraction
  layers.

  It provides a common API for all supported RDBMS. The main difference to most
  other DB abstraction packages is that MDB2 goes much further to ensure
  portability.


pkgId: 7c5fda2a39a6a4ef1b65c5a4539004ccf74e790e
name: php-pear-Mail-Mime
arch: src
version: 1.5.2
epoch: 0
release: 4
summary: Classes to create and decode mime messages
url: http://pear.php.net/package/Mail_Mime
rpm_license: PHP
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: php-pear-Mail-Mime-1.5.2-4.src.rpm
checksum_type: sha
description:
  A Package to enable easy creation of complex multipart emails. If you look for
  a simple API for creating such emails, then Mail_Mime class will probably
  suffice. Else you can use Mail_mimePart, which gives you better control about
  MIME creation


pkgId: 36c267212bbfbd63fa1635d85af717cd0be94ef2
name: php-pear-Mail-mimeDecode
arch: src
version: 1.5.0
epoch: 0
release: 4
summary: Class to decode mime messages
url: http://pear.php.net/package/Mail_mimeDecode
rpm_license: BSD
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: php-pear-Mail-mimeDecode-1.5.0-4.src.rpm
checksum_type: sha
description:
  Provides a class to deal with the decoding and interpreting of mime messages.
  This package used to be part of the Mail_Mime package, but has been split off.

  To run post-installation tests, execute:
  pear run-tests -p Mail_mimeDecode


pkgId: c175dc1f42e88e04289d435c046dccb99bb52b32
name: php-pear-Net-SMTP
arch: src
version: 1.3.1
epoch: 0
release: 1.ep
summary: Provides an implementation of the SMTP protocol
url: http://pear.php.net/package/Net_SMTP
rpm_license: PHP
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: php-pear-Net-SMTP-1.3.1-1.ep.src.rpm
checksum_type: sha
description:
  Provides an implementation of the SMTP protocol using PEAR's Net_Socket class.

  php-pear-Net-SMTP can optionally use package "php-pear-Auth-SASL".


pkgId: 0a7952955a0cf2853630dc89e3e98a918628f2f9
name: php-pear-Net-Socket
arch: src
version: 1.0.9
epoch: 0
release: 1
summary: Network Socket Interface
url: http://pear.php.net/package/Net_Socket
rpm_license: PHP
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: php-pear-Net-Socket-1.0.9-1.src.rpm
checksum_type: sha
description:
    Net_Socket is a class interface to TCP sockets.  It provides blocking
    and non-blocking operation, with different reading and writing modes
    (byte-wise, block-wise, line-wise and special formats like network
    byte-order ip addresses).


pkgId: 4134688b7e89b62af33d3e908a24f3f99e3a9a5b
name: php-pecl-Fileinfo
arch: src
version: 1.0.4
epoch: 0
release: 5
summary: Fileinfo is a PHP extension that wraps the libmagic library
url: http://pecl.php.net/package/Fileinfo
rpm_license: PHP
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Languages
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: php-pecl-Fileinfo-1.0.4-5.src.rpm
checksum_type: sha
description:
  This extension allows the retrieval of file type information for the vast
  majority of files.  This information may include such information as dimensions
  or compression quality of images, duration of sound files, etc...

  Additionally, it can also be used to retrieve the MIME type for a particular
  file, and for text files, the proper language encoding.


pkgId: 5a399e1b09f14519c96d61d8c34162f52e216847
name: php53-shim
arch: src
version: 5.3.3
epoch: 0
release: 1.2
summary: Bodge that provides php depending on php53
url: http://www.phcomp.co.uk/Downloads/php53-shim-5.3.3-1.2.src.rpm
rpm_license: GPL
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: php53-shim-5.3.3-1.2.src.rpm
checksum_type: sha
description:
  A shim to get packages requiring php installed on a RHEL 5.6+ system which has php53.
  The problem is that php53 does NOT provide php with the result that many packages
  that depend on php will not install.

  php-mbstring is also provided - it probably ought to be split into
  separate packages -- but I am too lazy & it works for me as it is.


pkgId: fd5cd5ce407d7bb73e62afadb9f09dc43a78a401
name: pnp4nagios
arch: src
version: 0.4.10
epoch: 0
release: 3
summary: Nagios performance data analysis tool
url: http://www.pnp4nagios.org/
rpm_license: GPLv2
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/System
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: pnp4nagios-0.4.10-3.src.rpm
checksum_type: sha
description:
  PNP is an addon to nagios which analyzes performance data provided by plugins
  and stores them automatically into RRD-databases.


pkgId: a3e0f2b924cabb2376fc13f81ba9e715a9f0c560
name: postgresql92
arch: src
version: 9.2.1
epoch: 0
release: 1PGDG.didt.ep
summary: PostgreSQL client programs and libraries
url: http://www.postgresql.org/
rpm_license: PostgreSQL
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/Databases
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: postgresql92-9.2.1-1PGDG.didt.ep.src.rpm
checksum_type: sha
description:
  PostgreSQL is an advanced Object-Relational database management system
  (DBMS) that supports almost all SQL constructs (including
  transactions, subselects and user-defined types and functions). The
  postgresql package includes the client programs and libraries that
  you'll need to access a PostgreSQL DBMS server.  These PostgreSQL
  client programs are programs that directly manipulate the internal
  structure of PostgreSQL databases on a PostgreSQL server. These client
  programs can be located on the same machine with the PostgreSQL
  server, or may be on a remote machine which accesses a PostgreSQL
  server over a network connection. This package contains the command-line
  utilities for managing PostgreSQL databases on a PostgreSQL server.

  If you want to manipulate a PostgreSQL database on a local or remote PostgreSQL
  server, you need this package. You also need to install this package
  if you're installing the postgresql92-server package.


pkgId: aa33b26b89a14aa5c1591c89ae01e44f0af99901
name: puppet
arch: src
version: 0.24.6
epoch: 0
release: 1.ep
summary: A network tool for managing many disparate systems
url: http://puppet.reductivelabs.com/
rpm_license: GPLv2+
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: System Environment/Base
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: puppet-0.24.6-1.ep.src.rpm
checksum_type: sha
description:
  Puppet lets you centrally manage every important aspect of your system using a
  cross-platform specification language that manages all the separate elements
  normally aggregated in different files, like users, cron jobs, and hosts,
  along with obviously discrete elements like packages, services, and files.


pkgId: e13440d2c0a1cdef6039e841c146ef920b728e86
name: python-docutils
arch: src
version: 0.7
epoch: 0
release: 3.ep
summary: System for processing plaintext documentation
url: http://docutils.sourceforge.net
rpm_license: Public Domain and MIT and Python and GPLv2
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Languages
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: python-docutils-0.7-3.ep.src.rpm
checksum_type: sha
description:
  The Docutils project specifies a plaintext markup language, reStructuredText,
  which is easy to read and quick to write.  The project includes a python
  library to parse rST files and transform them into other useful formats such
  as HTML, XML, and TeX as well as commandline tools that give the enduser
  access to this functionality.

  Currently, the library supports parsing rST that is in standalone files and
  PEPs (Python Enhancement Proposals).  Work is underway to parse rST from
  Python inline documentation modules and packages.


pkgId: 9611f206f4ffe9a38c00de6927edb97e86a7b8de
name: python-imaging
arch: src
version: 1.1.7
epoch: 0
release: 3.ep
summary: Python's own image processing library
url: http://www.pythonware.com/products/pil/
rpm_license: MIT
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: System Environment/Libraries
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: python-imaging-1.1.7-3.ep.src.rpm
checksum_type: sha
description:
  Python Imaging Library

  The Python Imaging Library (PIL) adds image processing capabilities
  to your Python interpreter.

  This library provides extensive file format support, an efficient
  internal representation, and powerful image processing capabilities.

  Notice that in order to reduce the package dependencies there are
  three subpackages: devel (for development); tk (to interact with the
  tk interface) and sane (scanning devices interface).


pkgId: 4a6c57c0490b1bd91a69be38bb8a68367008df76
name: python-setuptools
arch: src
version: 0.6.14
epoch: 0
release: 4.ep
summary: Easily build and distribute Python packages
url: http://pypi.python.org/pypi/distribute
rpm_license: Python or ZPLv2.0
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/System
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: python-setuptools-0.6.14-4.ep.src.rpm
checksum_type: sha
description:
  Setuptools is a collection of enhancements to the Python distutils that allow
  you to more easily build and distribute Python packages, especially ones that
  have dependencies on other packages.

  This package contains the runtime components of setuptools, necessary to
  execute the software that requires pkg_resources.py.

  This package contains the distribute fork of setuptools.


pkgId: 28a81799aea264fd923b609a6dda8633cfa19b56
name: qstat
arch: src
version: 2.11
epoch: 0
release: 5
summary: Real-time Game Server Status for FPS game servers
url: http://sourceforge.net/projects/qstat/
rpm_license: Artistic
rpm_vendor: End point Corporation
rpm_group: Amusements/Games
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: qstat-2.11-5.src.rpm
checksum_type: sha
description:
  QStat is a command-line program that gathers real-time statistics
  from Internet game servers. Most supported games are of the first
  person shooter variety (Quake, Half-Life, etc)


pkgId: 07d690bf2f15e7a661b272976a47db1aac0ba5c3
name: radiusclient
arch: src
version: 0.3.2
epoch: 0
release: 1
summary: framework and library for writing RADIUS clients
url: http://www.cityline.net/~lf/radius/
rpm_license: Free
rpm_vendor: End Point Corporation
rpm_group: Applications/Internet
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: Dag Wieers <dag@wieers.com>
location_href: radiusclient-0.3.2-1.src.rpm
checksum_type: sha
description:
  Radiusclient is a framework and library for writing RADIUS clients.
  The distribution contains a flexible RADIUS aware login replacement,
  a command line program to send RADIUS accounting records and a utility
  to query the status of a (Merit) RADIUS server. All these programs
  are based on a library which lets you develop your own RADIUS aware
  application in less than 50 lines of C code. It is highly portable
  and runs at least under Linux, a lot of BSD variants and Solaris.


pkgId: eeef95d7c980920067e575d0d3ab959e85218d14
name: radiusclient-ng
arch: src
version: 0.5.6
epoch: 0
release: 3.ep
summary: RADIUS protocol client library
url: http://developer.berlios.de/projects/radiusclient-ng/
rpm_license: BSD
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/Internet
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: radiusclient-ng-0.5.6-3.ep.src.rpm
checksum_type: sha
description:
  Portable, easy-to-use and standard compliant library suitable for
  developing free and commercial software that need support for a RADIUS
  protocol (RFCs 2128 and 2139).


pkgId: 26ac416a678fa7395d8703e8c5b307fc58fc1599
name: recode
arch: src
version: 3.6
epoch: 0
release: 24.ep
summary: Conversion between character sets and surfaces
url: http://recode.progiciels-bpi.ca/
rpm_license: GPL
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/File
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: recode-3.6-24.ep.src.rpm
checksum_type: sha
description:
  The `recode' converts files between character sets and usages.
  It recognises or produces nearly 150 different character sets
  and is able to transliterate files between almost any pair. When exact
  transliteration are not possible, it may get rid of the offending
  characters or fall back on approximations.  Most RFC 1345 character sets
  are supported.


pkgId: 018c1959cd0cbce0fcedfcead58e86e858884a25
name: roundcubemail
arch: src
version: 0.2
epoch: 0
release: 3.beta
summary: Round Cube Webmail is a browser-based multilingual IMAP client
url: http://www.roundcube.net
rpm_license: GPLv2
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Applications/System
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: roundcubemail-0.2-3.beta.src.rpm
checksum_type: sha
description:
  RoundCube Webmail is a browser-based multilingual IMAP client
  with an application-like user interface. It provides full
  functionality you expect from an e-mail client, including MIME
  support, address book, folder manipulation, message searching
  and spell checking. RoundCube Webmail is written in PHP and
  requires the MySQL database or the PostgreSQL database. The user
  interface is fully skinnable using XHTML and CSS 2.


pkgId: 0f1e8101053f71a3c264f0a2444d04c6cc2dbf85
name: rpmdevtools
arch: src
version: 5.3
epoch: 0
release: 1
summary: RPM Development Tools
url: http://fedora.redhat.com/
rpm_license: GPL
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Tools
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: rpmdevtools-5.3-1.src.rpm
checksum_type: sha
description:
  This package contains scripts and (X)Emacs support files to aid in
  development of RPM packages.
  rpmdev-setuptree    Create RPM build tree within user's home directory
  rpmdev-diff         Diff contents of two archives
  rpmdev-newspec      Creates new .spec from template
  rpmdev-rmdevelrpms  Find (and optionally remove) "development" RPMs
  rpmdev-checksig     Check package signatures using alternate RPM keyring
  rpminfo             Print information about executables and libraries
  rpmdev-md5          Display the md5sum of all files in an RPM
  rpmdev-vercmp       RPM version comparison checker
  spectool            Expand and download sources and patches in specfiles
  rpmdev-wipetree     Erase all files within dirs created by rpmdev-setuptree
  rpmdev-extract      Extract various archives, "tar xvf" style


pkgId: 93b96d5f67f646c98da57778236261b2c39fdee9
name: rpmdevtools
arch: src
version: 6.7
epoch: 0
release: 1
summary: RPM Development Tools
url: https://fedorahosted.org/rpmdevtools/
rpm_license: GPLv2+ and GPLv2
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Tools
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: rpmdevtools-6.7-1.src.rpm
checksum_type: sha
description:
  This package contains scripts and (X)Emacs support files to aid in
  development of RPM packages.
  rpmdev-setuptree    Create RPM build tree within user's home directory
  rpmdev-diff         Diff contents of two archives
  rpmdev-newspec      Creates new .spec from template
  rpmdev-rmdevelrpms  Find (and optionally remove) "development" RPMs
  rpmdev-checksig     Check package signatures using alternate RPM keyring
  rpminfo             Print information about executables and libraries
  rpmdev-md5          Display the md5sum of all files in an RPM
  rpmdev-vercmp       RPM version comparison checker
  spectool            Expand and download sources and patches in specfiles
  rpmdev-wipetree     Erase all files within dirs created by rpmdev-setuptree
  rpmdev-extract      Extract various archives, "tar xvf" style
  rpmdev-bumpspec     Bump revision in specfile
  ...and many more.


pkgId: bc5776c9834f586d5e2dbba13587027411ab193f
name: rpmlint
arch: src
version: 0.84
epoch: 0
release: 2
summary: Tool for checking common errors in RPM packages
url: http://rpmlint.zarb.org/
rpm_license: GPLv2
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Tools
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: rpmlint-0.84-2.src.rpm
checksum_type: sha
description:
  rpmlint is a tool for checking common errors in RPM packages.  Binary
  and source packages can be checked.


pkgId: 26e7697d298f9501d560b261878330c1ff4a06d2
name: rsyslog
arch: src
version: 3.21.3
epoch: 0
release: 3
summary: Enhanced system logging and kernel message trapping daemons
url: http://www.rsyslog.com/
rpm_license: GPLv3+
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: System Environment/Daemons
rpm_buildhost: sl4-rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: rsyslog-3.21.3-3.src.rpm
checksum_type: sha
description:
  Rsyslog is an enhanced multi-threaded syslogd supporting, among others, MySQL,
  syslog/tcp, RFC 3195, permitted sender lists, filtering on any message part,
  and fine grain output format control. It is quite compatible to stock sysklogd
  and can be used as a drop-in replacement. Its advanced features make it
  suitable for enterprise-class, encryption protected syslog relay chains while
  at the same time being very easy to setup for the novice user.


pkgId: fd4332b89b1447cdca4dc0e3a60d49fdc343ed8b
name: rsyslog
arch: src
version: 5.6.2
epoch: 0
release: 1.ep
summary: Enhanced system logging and kernel message trapping daemon
url: http://www.rsyslog.com/
rpm_license: GPLv3+
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: System Environment/Daemons
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point Hosting Team <hosting@endpoint.com>
location_href: rsyslog-5.6.2-1.ep.src.rpm
checksum_type: sha
description:
  Rsyslog is an enhanced, multi-threaded syslog daemon. It supports MySQL,
  syslog/TCP, RFC 3195, permitted sender lists, filtering on any message part,
  and fine grain output format control. It is compatible with stock sysklogd
  and can be used as a drop-in replacement. Rsyslog is simple to set up, with
  advanced features suitable for enterprise-class, encryption-protected syslog
  relay chains.


pkgId: 9eaa30660a2b9949f58e1a4a46629ec8cc0a0463
name: ruby-enterprise
arch: src
version: 1.8.6
epoch: 0
release: 3.ep
summary: Ruby Enterprise Edition (Release 20090520)
url: http://www.rubyenterpriseedition.com/
rpm_license: GPL
rpm_vendor: Phusion.nl
rpm_group: Development/Languages
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Adam Vollrath <adam@endpoint.com>
location_href: ruby-enterprise-1.8.6-3.ep.src.rpm
checksum_type: sha
description:
  Ruby Enterprise Edition is a server-oriented friendly branch of Ruby which includes various enhancements:
  * A copy-on-write friendly garbage collector. Phusion Passenger uses this, in combination with a technique called preforking, to reduce Ruby on Rails applications' memory usage by 33% on average.
  * An improved memory allocator called tcmalloc, which improves performance quite a bit.
  * The ability to tweak garbage collector settings for maximum server performance, and the ability to inspect the garbage collector's state. (RailsBench GC patch)
  * The ability to dump stack traces for all running threads (caller_for_all_threads), making it easier for one to debug multithreaded Ruby web applications.


pkgId: f0f5e23e0405f4c34093ee8555f3cb0f260a74d0
name: ruby-enterprise-opt-repo
arch: src
version: 1.0
epoch: 0
release: 1
summary: Yum configuration for End Point Ruby Enterprise 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: rhel5-build64.endpoint.com
rpm_packager: Adam Vollrath <hosting@endpoint.com>
location_href: ruby-enterprise-opt-repo-1.0-1.src.rpm
checksum_type: sha
description:
  This package contains the Yum configuration and public GnuPG signing keys
  for the End Point Ruby Enterprise Edition RPM repository.


pkgId: bcfba9e0d93f94c866c450a806320e0b2f0e0f8b
name: rubygem-rake
arch: src
version: 0.8.3
epoch: 0
release: 1.ep
summary: Ruby based make-like utility
url: http://rake.rubyforge.org
rpm_license: MIT
rpm_vendor: End Point Corporation https://packages.endpoint.com/
rpm_group: Development/Languages
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: End Point hosting team <hosting@endpoint.com>
location_href: rubygem-rake-0.8.3-1.ep.src.rpm
checksum_type: sha
description:
  Rake is a Make-like program implemented in Ruby. Tasks and dependencies are
  specified in standard Ruby syntax.


pkgId: 7a12c234b9fb65aaaa8d227c531294350d53af81
name: siege
arch: src
version: 2.67
epoch: 0
release: 1
summary: Siege is an http regression testing and benchmarking utility
url: http://www.joedog.org/JoeDog/Siege
rpm_license: GPLv2+
rpm_vendor: End Point Corporation
rpm_group: Development/Tools
rpm_buildhost: sl4-rhel5-build64.endpoint.com
location_href: siege-2.67-1.src.rpm
checksum_type: sha
description:
  Siege is an http regression testing and benchmarking utility.
  It was designed to let web developers measure the performance of their code
  under duress, to see how it will stand up to load on the internet.
  Siege supports basic authentication, cookies, HTTP and HTTPS protocols.
  It allows the user hit a web server with a configurable number of concurrent
  simulated users. Those users place the webserver "under siege."


pkgId: 354018ca16b837b5aad97dafb0f99537178e3710
name: snort
arch: src
version: 2.8.4.1
epoch: 1
release: 1.ep
summary: An open source Network Intrusion Detection System (NIDS)
url: http://www.snort.org/
rpm_license: GPL
rpm_vendor: Snort.org
rpm_group: Applications/Internet
rpm_buildhost: rhel5-build64.endpoint.com
rpm_packager: Snort.org RPMs
location_href: snort-2.8.4.1-1.ep.src.rpm
checksum_type: sha
description:
  Snort is an open source network intrusion detection system, capable of
  performing real-time traffic analysis and packet logging on IP networks.
  It can perform protocol analysis, content searching/matching and can be
  used to detect a variety of attacks and probes, such as buffer overflows,
  stealth port scans, CGI attacks, SMB probes, OS fingerprinting attempts,
  and much more.

  Snort has three primary uses. It can be used as a straight packet sniffer
  like tcpdump(1), a packet logger (useful for network traffic debugging,
  etc), or as a full blown network intrusion detection system.

  You MUST edit /etc/snort/snort.conf to configure snort before it will work!

  There are 5 different packages available. All of them require the base
  snort rpm (this one). Additionally, you may need to chose a different
  binary to install if you want database support.

  If you install a different binary package /usr/sbin/snort should end up
  being a symlink to a binary in one of the following configurations:

  	plain		Snort (this package, required)
  	mysql		Snort with mysql (optional)
  	postgresql	Snort with postgresql (optional)
  	unixODBC	Snort with unixODBC (optional)
  	oracle		Snort with oracle (optional, not official)
  	inline		Snort with inline support (optional)

  Please see the documentation in /usr/share/doc/snort-2.8.4.1 for more
  information on snort features and configuration.


