[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

libdevel-globaldestruction-perl_0.02-1~bpo50+1_i386.changes is NEW

(new) libdevel-globaldestruction-perl_0.02-1~bpo50+1.diff.gz optional perl
(new) libdevel-globaldestruction-perl_0.02-1~bpo50+1.dsc optional perl
(new) libdevel-globaldestruction-perl_0.02-1~bpo50+1_i386.deb optional perl
Expose PL_dirty, the flag which marks global destruction
 Perl's global destruction is a little tricky to deal with WRT finalizers
 because it's not ordered and objects can sometimes disappear.
 Writing defensive destructors is hard and annoying, and usually if global
 destruction is happenning you only need the destructors that free up non
 process local resources to actually execute.
 For these constructors you can avoid the mess by simply bailing out if global
 destruction is in effect.
(new) libdevel-globaldestruction-perl_0.02.orig.tar.gz optional perl
Changes: libdevel-globaldestruction-perl (0.02-1~bpo50+1) lenny-backports; urgency=low
  * Rebuild for lenny-backports.

Override entries for your package:

Announcing to backports-changes@lists.backports.org

Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.
xist in other distributions.

Reply to: