#
# spec file for package perl-Catalyst-Model-Adaptor (Version 0.09)
#
# Copyright (c) 2010 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-Catalyst-Model-Adaptor
Version:        0.09
Release:        1
License:        GPL+ or Artistic
%define cpan_name Catalyst-Model-Adaptor
Summary:        use a plain class as a Catalyst model
Url:            http://search.cpan.org/dist/Catalyst-Model-Adaptor/
Group:          Development/Libraries/Perl
#Source:         http://www.cpan.org/authors/id/B/BO/BOBTFISH/Catalyst-Model-Adaptor-%{version}.tar.gz
Source:         %{cpan_name}-%{version}.tar.bz2
BuildRequires:  perl(Catalyst::Runtime)
BuildRequires:  perl(MRO::Compat)
BuildRequires:  perl(ok)
BuildRequires:  perl
BuildRequires:  perl-macros
Requires:       perl(Catalyst::Runtime)
Requires:       perl(MRO::Compat)
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildArch:      noarch
%{perl_requires}

%description
The idea is that you don't want your Catalyst model to be anything other
than a line or two of glue. Using this module ensures that your Model
classes are separate from your application and therefore are
well-abstracted, reusable, and easily testable.

Right now there are too many modules on CPAN that are Catalyst-specific.
Most of the models would be better written as a class that handles most of
the functionality with just a bit of glue to make it work nicely with
Catalyst. This module aims to make integrating your class with Catalyst
trivial, so you won't have to do any extra work to make your model generic.

For a good example of a Model that takes the right design approach, take a
look at Catalyst::Model::DBIC::Schema. All it does is glues an existing
DBIx::Class::Schema to Catalyst. It provides a bit of sugar, but no actual
functionality. Everything important happens in the 'DBIx::Class::Schema'
object.

The end result of that is that you can use your app's DBIC schema without
ever thinking about Catalyst. This is a Good Thing.

Catalyst is glue, not a way of life!

%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

%changelog