Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#9164 closed enhancement (fixed)

gmime-3.0.2 (wait for balsa to use it)

Reported by: bdubbs@… Owned by: DJ Lucas
Priority: normal Milestone: hold
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

New major version. We'll need to look at this closely.

Change History (10)

comment:1 by bdubbs@…, 5 years ago

Owner: changed from blfs-book@… to bdubbs@…
Status: newassigned

comment:2 by bdubbs@…, 5 years ago

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.

comment:3 by bdubbs@…, 5 years ago

Milestone: 8.1hold
Owner: changed from bdubbs@… to blfs-book@…
Status: assignednew

Move to hold until a package in BLFS can use it. Currently only totem-pl-parser and balsa use this package.

comment:4 by bdubbs@…, 5 years ago

Milestone: holdy-hold

Milestone renamed

comment:5 by Armin K, 5 years ago

Milestone: y-hold8.2
Summary: gmime-3.0.0gmime-3.0.2

totem-pl-parser-3.26.0 has been released and can use this version. No other users are known to me.

comment:6 by Armin K, 5 years ago

Hm, there's also balsa, but it still can't use 3.0, only 2.6. totem-pl-parser-3.26.0, although using meson now, can use either gmime 2.6 or 3.0.

comment:7 by bdubbs@…, 5 years ago

Milestone: 8.2y-hold
Summary: gmime-3.0.2gmime-3.0.2 (wait for balsa to use it)

Moving back to hold. I looked at balsa and the devs seem to be more interested in meson than GMime3. Since both the packages can use gmime 2.6, there is no rush. Will look again when balsa make it's next release.

comment:8 by DJ Lucas, 5 years ago

Owner: changed from blfs-book@… to DJ Lucas
Status: newassigned

comment:9 by DJ Lucas, 5 years ago

Resolution: fixed
Status: assignedclosed

Versions coexist fine and downstream consumers of totem-pl-parser also check for 3.0. Fixed in r19364.

comment:10 by Bruce Dubbs, 4 years ago

Milestone: y-holdhold

Milestone renamed

Note: See TracTickets for help on using tickets.