a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
Updated DESCR
Upstream changes:
3.020000 July 2012
* new destructor_method option
3.018000 June 2012
* new options ignore_preds, ignore_object, ignore_objects
3.016000 May 2012
* new ignore_class and ignore_classes options
3.014000 February 2012
* tests force Dumper sortkeys
3.012000 February 2012
* tests allow for "at line 123." with a "."
3.010000 February 2012
* constructor can return multiple values
3.008000 January 2012
* Try for Perl 5.6.0 too.
* XSUB bits in the main docs.
* Slightly more compact SYNOPSIS.
3.007_001 Sun Jan 6 19:58:00 PST 2012
* Cope with some tied glob warnings of perl 5.14 and up.
3.007_000 Sun Jan 1 17:29:41 PST 2012
* New developer's release
* Add Kevin Ryde's XSUB doc
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
dependency for scheduled update of textproc/p5-XML-RAI to 1.3031.
A memory leak occurs when a Perl data structure is destroyed but some of
the contents of that structure are not freed. Leaked memory is a useless
overhead. Leaks can significantly impact system performance. They can also
cause an application to abend due to lack of memory.
In Perl, circular references are a common cause of memory leaks. Circular
references are allowed in Perl, but data structures containing circular
references will leak memory unless the programmer takes specific measures
to prevent leaks. Preventive measures include weakening the references
and arranging to break the reference cycle just before the structure is
destroyed.
When using circular references, it is easy to misdesign or misimplement a
scheme for preventing memory leaks. Mistakes of this kind have been hard to
detect in a test suite.
Test::Weaken allows easy detection of unfreed Perl data. Test::Weaken allows
you to examine the unfreed data, even data that would usually have been made
inaccessible.
Test::Weaken frees the test structure, then looks to see if any of the
contents of the structure were not actually deallocated. By default,
Test::Weaken determines the contents of a data structure by examining
arrays and hashes, by following references, and by following tied variables
to their underlying object. Test::Weaken does this recursively to unlimited
depth.
Test::Weaken can deal with circular references without going into infinite
loops. Test::Weaken will not visit the same Perl data object twice.
