Hello community,

here is the log from the commit of package perl-Test-Base for openSUSE:Factory
checked in at Wed Apr 6 14:56:27 CEST 2011.



--------
--- perl-Test-Base/perl-Test-Base.changes       2011-03-16 13:42:30.000000000 
+0100
+++ /mounts/work_src_done/STABLE/perl-Test-Base/perl-Test-Base.changes  
2011-04-06 13:49:01.000000000 +0200
@@ -1,0 +2,7 @@
+Wed Apr  6 10:47:23 UTC 2011 - [email protected]
+
+- updated to 0.60
+  - Applied patch by andk++
+  - Make regexp test skip on 5.14 for now.
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


Old:
----
  Test-Base-0.59.tar.bz2

New:
----
  Test-Base-0.60.tar.gz

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

Other differences:
------------------
++++++ perl-Test-Base.spec ++++++
--- /var/tmp/diff_new_pack.Uy9FeF/_old  2011-04-06 14:55:25.000000000 +0200
+++ /var/tmp/diff_new_pack.Uy9FeF/_new  2011-04-06 14:55:25.000000000 +0200
@@ -15,64 +15,63 @@
 # Please submit bugfixes or comments via http://bugs.opensuse.org/
 #
 
-# norootforbuild
 
 
 Name:           perl-Test-Base
-%define cpan_name %( echo %{name} | %{__sed} -e 's,perl-,,' )
-Summary:        A Data Driven Testing Framework
-Version:        0.59
-Release:        12
+Version:        0.60
+Release:        1
 License:        GPL+ or Artistic
+%define cpan_name Test-Base
+Summary:        A Data Driven Testing Framework
+Url:            http://search.cpan.org/dist/Test-Base/
 Group:          Development/Libraries/Perl
-Url:            http://search.cpan.org/dist/Test-Base
-Source:         %{cpan_name}-%{version}.tar.bz2
+#Source:         
http://www.cpan.org/authors/id/I/IN/INGY/Test-Base-%{version}.tar.gz
+Source:         %{cpan_name}-%{version}.tar.gz
+BuildArch:      noarch
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
-%{perl_requires}
-#!BuildIgnore:  perl-Test-Base
 BuildRequires:  perl
 BuildRequires:  perl-macros
-BuildRequires:  perl(Test::More) >= 0.62
-#
-BuildRequires:  perl(Algorithm::Diff) >= 1.15
 BuildRequires:  perl(Spiffy) >= 0.30
 BuildRequires:  perl(Test::Deep)
-BuildRequires:  perl(Text::Diff) >= 0.35
-BuildRequires:  perl(YAML)
-Requires:       perl(Algorithm::Diff) >= 1.15
-Requires:       perl(LWP::Simple)
 Requires:       perl(Spiffy) >= 0.30
 Requires:       perl(Test::Deep)
-Requires:       perl(Text::Diff) >= 0.35
-Requires:       perl(YAML)
-Provides:       %{cpan_name}
+%{perl_requires}
 
 %description
-Testing is usually the ugly part of Perl module authoring. Perl gives
-you a standard way to run tests with Test::Harness, and basic testing
-primitives with Test::More. After that you are pretty much on your own
-to develop a testing framework and philosophy. Test::More encourages you
-to make your own framework by subclassing Test::Builder, but that is not
-trivial.
+Testing is usually the ugly part of Perl module authoring. Perl gives you a
+standard way to run tests with Test::Harness, and basic testing primitives
+with Test::More. After that you are pretty much on your own to develop a
+testing framework and philosophy. Test::More encourages you to make your
+own framework by subclassing Test::Builder, but that is not trivial.
 
-Test::Base gives you a way to write your own test framework base class
-that *is* trivial. In fact it is as simple as two lines:
+Test::Base gives you a way to write your own test framework base class that
+_is_ trivial. In fact it is as simple as two lines:
 
     package MyTestFramework;
     use Test::Base -Base;
 
-A module called "MyTestFramework.pm" containing those two lines, will
-give all the power of Test::More and all the power of Test::Base to
-every test file that uses it. As you build up the capabilities of
-"MyTestFramework", your tests will have all of that power as well.
-
-  Author:      Brian Ingerson <[email protected]>
+A module called 'MyTestFramework.pm' containing those two lines, will give
+all the power of Test::More and all the power of Test::Base to every test
+file that uses it. As you build up the capabilities of 'MyTestFramework',
+your tests will have all of that power as well.
+
+'MyTestFramework' becomes a place for you to put all of your reusable
+testing bits. As you write tests, you will see patterns and duplication,
+and you can "upstream" them into 'MyTestFramework'. Of course, you don't
+have to subclass Test::Base at all. You can use it directly in many
+applications, including everywhere you would use Test::More.
+
+Test::Base concentrates on offering reusable data driven patterns, so that
+you can write tests with a minimum of code. At the heart of all testing you
+have inputs, processes and expected outputs. Test::Base provides some clean
+ways for you to express your input and expected output data, so you can
+spend your time focusing on that rather than your code scaffolding.
 
 %prep
 %setup -q -n %{cpan_name}-%{version}
 
 %build
-perl Makefile.PL OPTIMIZE="$RPM_OPT_FLAGS -Wall"
+%{__perl} Makefile.PL INSTALLDIRS=vendor
 %{__make} %{?_smp_mflags}
 
 %check
@@ -84,11 +83,10 @@
 %perl_gen_filelist
 
 %clean 
-%{__rm} -rf $RPM_BUILD_ROOT
+%{__rm} -rf %{buildroot}
 
 %files -f %{name}.files
-# normally you only need to check for doc files
-%defattr(-,root,root)
+%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]

Reply via email to