Hello community,
here is the log from the commit of package perl-Test-LeakTrace for
openSUSE:Factory
checked in at Tue May 31 13:36:46 CEST 2011.
--------
--- perl-Test-LeakTrace/perl-Test-LeakTrace.changes 2011-03-15
10:55:15.000000000 +0100
+++
/mounts/work_src_done/STABLE/perl-Test-LeakTrace/perl-Test-LeakTrace.changes
2011-05-01 13:01:41.000000000 +0200
@@ -1,0 +2,11 @@
+Sun May 1 10:39:25 UTC 2011 - [email protected]
+
+- updated to 0.13
+ - Fix tests for older perls
+
+ - Use ">= 0", instead of "== 0" for no_leaks_ok()
+ - Add count_sv() to count all the SVs in a perl interpreter
+
+ - Resolve RT #58133: "False-positive related to XS code"
+
+-------------------------------------------------------------------
calling whatdependson for head-i586
Old:
----
Test-LeakTrace-0.10.tar.bz2
New:
----
Test-LeakTrace-0.13.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ perl-Test-LeakTrace.spec ++++++
--- /var/tmp/diff_new_pack.YIAQAV/_old 2011-05-31 13:36:10.000000000 +0200
+++ /var/tmp/diff_new_pack.YIAQAV/_new 2011-05-31 13:36:10.000000000 +0200
@@ -15,47 +15,43 @@
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
-# norootforbuild
Name: perl-Test-LeakTrace
-%define real_name %( echo %{name} | %{__sed} -e 's,perl-,,' )
+Version: 0.13
+Release: 1
+License: GPL+ or Artistic
+%define cpan_name Test-LeakTrace
Summary: Traces memory leaks
-Url: http://search.cpan.org/perldoc?Test::LeakTrace
+Url: http://search.cpan.org/dist/Test-LeakTrace/
Group: Development/Libraries/Perl
-License: GPL+ or Artistic
-Version: 0.10
-Release: 8
-Source: %{real_name}-%{version}.tar.bz2
-BuildRequires: perl-macros
+Source:
http://www.cpan.org/authors/id/G/GF/GFUJI/%{cpan_name}-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-build
+BuildRequires: perl
+BuildRequires: perl-macros
%{perl_requires}
%description
-Test::LeakTrace provides several functions that trace memory leaks. This module
-scans arenas, the memory allocation system, so it can detect any leaked SVs in
-given blocks.
-
-Leaked SVs are SVs which are not released after the end of the scope they have
-been created. These SVs include global variables and internal caches. For
-example, if you call a method in a tracing block, perl might prepare a cache
-for the method. Thus, to trace true leaks, no_leaks_ok() and leaks_cmp_ok()
-executes a block more than once.e
-
-Author:
--------
- Goro Fuji(gfx) <gfuji(at)cpan.org>.
-
+'Test::LeakTrace' provides several functions that trace memory leaks. This
+module scans arenas, the memory allocation system, so it can detect any
+leaked SVs in given blocks.
+
+*Leaked SVs* are SVs which are not released after the end of the scope they
+have been created. These SVs include global variables and internal caches.
+For example, if you call a method in a tracing block, perl might prepare a
+cache for the method. Thus, to trace true leaks, 'no_leaks_ok()' and
+'leaks_cmp_ok()' executes a block more than once.
%prep
-%setup -q -n %{real_name}-%{version}
+%setup -q -n %{cpan_name}-%{version}
+find . -type f -print0 | xargs -0 chmod 644
%build
-perl Makefile.PL
-make %{?jobs:-j%jobs}
+%{__perl} Makefile.PL INSTALLDIRS=vendor OPTIMIZE="%{optflags}"
+%{__make} %{?_smp_mflags}
%check
-make test
+%{__make} test
%install
%perl_make_install
@@ -63,10 +59,10 @@
%perl_gen_filelist
%clean
-rm -rf %{buildroot}
+%{__rm} -rf %{buildroot}
%files -f %{name}.files
-%defattr(0644, root, root, 0755)
-%doc Changes README MANIFEST
+%defattr(-,root,root,755)
+%doc Changes README
%changelog
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Remember to have fun...
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
