Changes 2.4.18:

GMime 2.4 has had a number of API changes since GMime 2.2. To start, ALL public
APIs that used to use off_t in GMime 2.2 now use gint64 so that the API and ABI
do not change based on whether or not large file support is enabled.

In addition, all of the functions marked as deprecated in 2.0 and 2.2 were
removed (usually they had equivalent functionality in a parent class).

Many functions have also been renamed for better clarity and/or consistency.
For convenience, GMime 2.4 source packages include a shell-script to aid in
porting applications using GMime 2.2 (should work for most GMime 2.0
applications as well) to the 2.4 API. You can find this script under the
tools/ directory, named `gmime-port-2-2-to-2-4.sh'.

This script won't fix everything, but it should help quite a bit.

1 files changed, 24 insertions, 29 deletions

diff --git a/mail/gmime/DESCR b/mail/gmime/DESCR
index 9238064afd0..69b83606d65 100644
--- a/mail/gmime/DESCR
+++ b/mail/gmime/DESCR
@@ -1,29 +1,24 @@
-GMime is a set of utilities for parsing and creating messages using
-the Multipurpose Internet Mail Extension (MIME) as defined by the
-following RFCs:
-
- * 0822: Standard for the Format of Arpa Internet Text Messages
- * 1521: MIME (Multipurpose Internet Mail Extensions) Part One:
-         Mechanisms for Specifying and Describing the Format of
-         Internet Message Bodies
- * 1847: Security Multiparts for MIME: Multipart/Signed and
-         Multipart/Encrypted
- * 1864: The Content-MD5 Header Field (Obsoletes rfc1544)
- * 2015: MIME Security with Pretty Good Privacy (PGP)
- * 2045: Multipurpose Internet Mail Extensions (MIME) Part One:
-         Format of Internet Message Bodies
- * 2046: Multipurpose Internet Mail Extensions (MIME) Part Two:
-         Media Types
- * 2047: Multipurpose Internet Mail Extensions (MIME) Part Three:
-         Message Header Extensions for Non-ASCII Text
- * 2048: Multipurpose Internet Mail Extensions (MIME) Part Four:
-         Registration Procedures
- * 2049: Multipurpose Internet Mail Extensions (MIME) Part Five:
-         Conformance Criteria and Examples
- * 2183: Communicating Presentation Information in Internet Messages:
-         The Content-Disposition Header Field
- * 2184: MIME Parameter Value and Encoded Word Extensions: Character
-         Sets, Languages, and Continuations
- * 2231: MIME Parameter Value and Encoded Word Extensions: Character
-         Sets, Languages, and Continuations (Obsoletes rfc2184)
- * 3156: MIME Security with OpenPGP (Updates rfc2015)
+GMime is a set of utilities for parsing and creating messages using the
+Multipurpose Internet Mail Extension (MIME) as defined by the following RFCs:
+* 0822: Standard for the Format of Arpa Internet Text Messages
+* 1521: MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for
+        Specifying and Describing the Format of Internet Message Bodies
+* 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
+* 1864: The Content-MD5 Header Field (Obsoletes rfc1544)
+* 2015: MIME Security with Pretty Good Privacy (PGP)
+* 2045: Multipurpose Internet Mail Extensions (MIME) Part One:
+        Format of Internet Message Bodies
+* 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
+* 2047: Multipurpose Internet Mail Extensions (MIME) Part Three:
+        Message Header Extensions for Non-ASCII Text
+* 2048: Multipurpose Internet Mail Extensions (MIME) Part Four:
+        Registration Procedures
+* 2049: Multipurpose Internet Mail Extensions (MIME) Part Five:
+        Conformance Criteria and Examples
+* 2183: Communicating Presentation Information in Internet Messages:
+        The Content-Disposition Header Field
+* 2184: MIME Parameter Value and Encoded Word Extensions: Character
+        Sets, Languages, and Continuations
+* 2231: MIME Parameter Value and Encoded Word Extensions: Character
+        Sets, Languages, and Continuations (Obsoletes rfc2184)
+* 3156: MIME Security with OpenPGP (Updates rfc2015)