libhash-merge-perl 0.12-2 source package in Ubuntu

Changelog

libhash-merge-perl (0.12-2) unstable; urgency=low
  * Take over (see http://lists.debian.org/debian-perl/2011/07/msg00003.html).  * Added Homepage and Vcs-* fields in d/control.  * Bump to 3.9.2 Standard-Version.  * Add myself to Uploaders and Copyright.  * Switch d/compat to 8.  * Build-Depends: switch to debhelper (>= 8).  * Switch to DEP5 license format. -- Fabrizio Regalli <email address hidden>  Sat, 02 Jul 2011 01:20:18 +0200

Upload details

Uploaded by:
Debian Perl Group
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
all
Section:
perl
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Precise release universe perl

Builds

Oneiric: [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
libhash-merge-perl_0.12-2.dsc 2.0 KiB 0e062064b81caa2704816d19c88b3a7f27af137b7766d8255a725cf88a2a2bbc
libhash-merge-perl_0.12.orig.tar.gz 8.4 KiB 1fa5de9d2d27adb8172b0b9429c1bdf16dc22c53305d47fac010f3dea86f071e
libhash-merge-perl_0.12-2.debian.tar.gz 2.4 KiB 5cc88ba9dadf89d5d13707a51eacbf6ff13a0a1d6c8679e52580836066cd73b1

No changes file available.

Binary packages built by this source

libhash-merge-perl: Perl module for merging arbitrarily deep hashes into a single hash

 Hash::Merge merges two arbitrarily deep hashes into a single hash. That
 is, at any level, it will add non-conflicting key-value pairs from one
 hash to the other, and follows a set of specific rules when there are key
 value conflicts (as outlined below). The hash is followed recursively,
 so that deeply nested hashes that are at the same level will be merged
 when the parent hashes are merged. Please note that self-referencing
 hashes, or recursive references, are not handled well by this method.
 .
 Values in hashes are considered to be either ARRAY references,
 HASH references, or otherwise are treated as SCALARs. By default, the
 data passed to the merge function will be cloned using the Clone module;
 however, if necessary, this behavior can be changed to use as many of
 the original values as possible. (See set_clone_behavior).