#9164: gmime-3.0.0
-------------------------+-----------------------
Reporter: bdubbs@… | Owner: bdubbs@…
Type: enhancement | Status: assigned
Priority: normal | Milestone: 8.1
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: |
-------------------------+-----------------------
Comment (by bdubbs@…):
Noteworthy changes in version 3.0.0
===================================
* Overhauled the GnuPG support to use GPGME under the hood rather than a
custom wrapper.
- Added S/MIME support, also thanks to GPGME.
- Added International Domain Name support via GNU's libidn.
* Improved the GMimeMessage APIs for accessing the common address headers.
They now all return an InternetAddressList.
* g_mime_init() no longer takes any flag arguments and the
g_mime_set_user_charsets() API has also been dropped. Instead,
GMimeParserOptions and GMimeFormatOptions have taken the place of these
APIs to allow customization of various parser and formatting options in a
much cleaner way. To facilitate this, many parsing functions and
formatting functions have changed to now take these options arguments.
* InternetAddress now has a 'charset' property that can be set to override
GMime's auto-detection of the best charset to use when encoding names.
* GMimeHeaderIter has been dropped in favor of a much simpler index-based
API on GMimeHeaderList.
* GMimeHeaderList no longer caches the raw message/mime headers in a
stream. Instead, each GMimeHeader now has its own cache. This means that
changing the GMimeHeaderList or any of its GMimeHeaders no longer
invalidates the entire cache.
* GMimeParser has been fixed to preserve (munged or otherwise) From-lines
that sometimes appear at the start of the content of message/rfc822 parts.
* GMimeParser now also scans for encapsulated PGP blocks within MIME parts
as it is parsing them and sets a flag on each GMimePart that contains one
of these blocks.
* GMimePart now has APIs for dealing with said encapsulated PGP blocks.
Developers interested in migrating to the upcoming GMime 3.0 API should
take a look at the PORTING document included with the source code as it
contains a fairly comprehensive list of the API changes that they will
need to be aware of.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/9164#comment:2>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
