Hello community,

here is the log from the commit of package perl-Carp-Always for openSUSE:Factory
checked in at Thu Apr 21 12:41:19 CEST 2011.



--------
New Changes file:

--- /dev/null   2010-08-26 16:28:41.000000000 +0200
+++ /mounts/work_src_done/STABLE/perl-Carp-Always/perl-Carp-Always.changes      
2011-01-14 12:31:02.000000000 +0100
@@ -0,0 +1,6 @@
+-------------------------------------------------------------------
+Fri Jan 14 11:30:38 UTC 2011 - [email protected]
+
+- initial package 0.09
+  * created by cpanspec 1.78.03
+

calling whatdependson for head-i586


New:
----
  Carp-Always-0.09.tar.bz2
  perl-Carp-Always.changes
  perl-Carp-Always.spec

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ perl-Carp-Always.spec ++++++
#
# spec file for package perl-Carp-Always
#
# Copyright (c) 2011 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via http://bugs.opensuse.org/
#



Name:           perl-Carp-Always
Version:        0.09
Release:        1
License:        GPL+ or Artistic
%define cpan_name Carp-Always
Summary:        Warns and dies noisily with stack backtraces
Url:            http://search.cpan.org/dist/Carp-Always/
Group:          Development/Libraries/Perl
#Source:         
http://www.cpan.org/authors/id/F/FE/FERREIRA/Carp-Always-%{version}.tar.gz
Source:         %{cpan_name}-%{version}.tar.bz2
BuildRequires:  perl(Carp)
BuildRequires:  perl(Test::Base)
BuildRequires:  perl(Test::Pod) >= 1.18
BuildRequires:  perl(Test::Pod::Coverage) >= 1.04
BuildRequires:  perl
BuildRequires:  perl-macros
Requires:       perl(Carp)
Requires:       perl(Test::Base)
Requires:       perl(Test::Pod) >= 1.18
Requires:       perl(Test::Pod::Coverage) >= 1.04
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildArch:      noarch
%{perl_requires}

%description
This module is meant as a debugging aid. It can be used to make a script
complain loudly with stack backtraces when warn()ing or die()ing.

Here are how stack backtraces produced by this module looks:

  # it works for explicit die's and warn's
  $ perl -MCarp::Always -e 'sub f { die "arghh" }; sub g { f }; g'
  arghh at -e line 1
          main::f() called at -e line 1
          main::g() called at -e line 1

  # it works for interpreter-thrown failures
  $ perl -MCarp::Always -w -e 'sub f { $a = shift; @a = @$a };' \
                           -e 'sub g { f(undef) }; g'
  Use of uninitialized value in array dereference at -e line 1
          main::f('undef') called at -e line 2
          main::g() called at -e line 2

In the implementation, the 'Carp' module does the heavy work, through
'longmess()'. The actual implementation sets the signal hooks
'$SIG{__WARN__}' and '$SIG{__DIE__}' to emit the stack backtraces.

Oh, by the way, 'carp' and 'croak' when requiring/using the 'Carp' module
are also made verbose, behaving like 'cloak' and 'confess', respectively.

EXPORT
    Nothing at all is exported.

%prep
%setup -q -n %{cpan_name}-%{version}

%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
%{__make} %{?_smp_mflags}

%check
%{__make} test

%install
%perl_make_install
%perl_process_packlist
%perl_gen_filelist

%clean
%{__rm} -rf %{buildroot}

%files -f %{name}.files
%defattr(644,root,root,755)
%doc Changes README

%changelog

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



Remember to have fun...

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to