Upstream changes:
3.008 2014-12-27 18:36:19-05:00 America/New_York
- make results of get_body be the same on Email::{Simple,MIME}
- ...but this method is a mess, so maybe avoid using Abstract for body
work
3.007 2013-12-31 10:39:14 America/New_York
fix skip count when MIME::Entity is not present
Change from previous:
3.004 2011-02-18
If present, MIME::Entity must be v5.501; v5.500 had a regression (or
a bug fix, depending how you look at it) that broke header-reading.
While technically older versions that are not 5.500 would work, it is
much simpler to just require the newest version, rather than to
support a version range with a hole in it.
pkgsrc changes:
- tidy
- add license definition
- adjust dependencies
Upstream changes:
3.002 2010-06-11
avoid a warning in MailInternet with zero headers found
Pkgsrc changes:
- The package supports installation to DESTDIR.
- This is purely a Perl module.
Changes since version 2.131:
============================
2.132 2007-03-22
packaging improvements
Changes:
2.131 2006-08-22
- pod tests
2.13 2006-07-24
- test for and permit passing Email::Abstract objects to Email::Abstract
class methods
2.12 2006-07-24
- don't use MIME::Entity in test if it's not available
2.11 2006-07-22
- better test planning
2.10 2006-07-21
- add a new method to create wrapper objects
- handle subclasses /properly/ (correct ISA order)
- improved tests and test coverage
- miscellaneous refactoring
- update PEP URL
- update documentation
"Email::Abstract" provides module writers with the ability to write
representation-independent mail handling code. For instance, in
the cases of "Mail::Thread" or "Mail::ListDetector", a key part of
the code involves reading the headers from a mail object. Where
previously one would either have to specify the mail class required,
or to build a new object from scratch, "Email::Abstract" can be
used to perform certain simple operations on an object regardless
of its underlying representation.
"Email::Abstract" currently supports "Mail::Internet", "MIME::Entity",
"Mail::Message", "Email::Simple" and "Email::MIME". Other
representations are encouraged to create their own "Email::Abstract::*"
class by copying "Email::Abstract::EmailSimple". All modules
installed under the "Email::Abstract" hierarchy will be automatically
picked up and used.
