File perl-Email-MIME-Kit.spec of Package perl-Email-MIME-Kit

Overview Repositories Revisions Requests Users Attributes Meta

File perl-Email-MIME-Kit.spec of Package perl-Email-MIME-Kit (Revision 4ee75221f876cd1f7010e1219f9f9a5c)

Currently displaying revision 4ee75221f876cd1f7010e1219f9f9a5c , Show latest

#
# spec file for package perl-Email-MIME-Kit (Version 2.102010)
#
# 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-Email-MIME-Kit
Version:        2.102010
Release:        1
License:        GPL+ or Artistic
%define cpan_name Email-MIME-Kit
Summary:        build messages from templates
Url:            http://search.cpan.org/dist/Email-MIME-Kit/
Group:          Development/Libraries/Perl
#Source:         http://www.cpan.org/authors/id/R/RJ/RJBS/Email-MIME-Kit-%{version}.tar.gz
Source:         %{cpan_name}-%{version}.tar.bz2
BuildRequires:  perl(Email::MessageID) >= 1.400
BuildRequires:  perl(Email::MIME) >= 1.900
BuildRequires:  perl(Email::MIME::Creator)
BuildRequires:  perl(File::Basename)
BuildRequires:  perl(File::Spec)
BuildRequires:  perl(JSON) >= 2
BuildRequires:  perl(Moose) >= 0.65
BuildRequires:  perl(Moose::Role)
BuildRequires:  perl(Moose::Util::TypeConstraints)
BuildRequires:  perl(String::RewritePrefix)
BuildRequires:  perl(Test::Deep)
BuildRequires:  perl(utf8)
BuildRequires:  perl(YAML::XS)
BuildRequires:  perl
BuildRequires:  perl-macros
Requires:       perl(Email::MessageID) >= 1.400
Requires:       perl(Email::MIME) >= 1.900
Requires:       perl(Email::MIME::Creator)
Requires:       perl(File::Basename)
Requires:       perl(File::Spec)
Requires:       perl(JSON) >= 2
Requires:       perl(Moose) >= 0.65
Requires:       perl(Moose::Role)
Requires:       perl(Moose::Util::TypeConstraints)
Requires:       perl(String::RewritePrefix)
Requires:       perl(Test::Deep)
Requires:       perl(YAML::XS)
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildArch:      noarch
%{perl_requires}

%description
Email::MIME::Kit is a templating system for email messages. Instead of
trying to be yet another templating system for chunks of text, it makes it
easy to build complete email messages.

It handles the construction of multipart messages, text and HTML
alternatives, attachments, interpart linking, string encoding, and
parameter validation.

Although nearly every part of Email::MIME::Kit is a replaceable component,
the stock configuration is probably enough for most use. A message kit will
be stored as a directory that might look like this:

sample.mkit/
    manifest.json
    body.txt
    body.html
    logo.jpg

The manifest file tells Email::MIME::Kit how to put it all together, and
might look something like this:

{
    "renderer": "TT",
    "header": [
      { "From": "WY Corp <noreplies@wy.example.com>" },
      { "Subject": "Welcome aboard, [% recruit.name %]!" }
    ],
    "alternatives": [
      { "type": "text/plain", "path": "body.txt" },
      {
        "type": "text/html",
        "path": "body.html",
        "container_type": "multipart/related",
        "attachments": [ { "type": "image/jpeg", "path": "logo.jpg" } ]
      }
    ]
  }

*Please note:* the assembly of HTML documents as multipart/related bodies
will probably be simplified with an alternate assembler in the near future.

The above manifest would build a multipart alternative message. GUI mail
clients would see a rendered HTML document with the logo graphic visible
from the attachment. Text mail clients would see the plaintext.

Both the HTML and text parts would be rendered using the named renderer,
which here is Template-Toolkit.

The message would be assembled and returned as an Email::MIME object, just
as easily as suggested in the the /SYNOPSIS manpage above.

%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 dist.ini LICENSE README

%changelog

Places

File perl-Email-MIME-Kit.spec of Package perl-Email-MIME-Kit (Revision 4ee75221f876cd1f7010e1219f9f9a5c)

Places