<metapackage xmlns:os="http://opensuse.org/Standards/One_Click_Install" xmlns="http://opensuse.org/Standards/One_Click_Install">
<group distversion="SUSE Linux Enterprise Server 15 SP2">
    <name>SUSE Package Hub 15 SP2 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP2-Backports-Pool</name>
        <summary>Package Hub 15 SP2</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  <group distversion="SUSE Linux Enterprise Desktop 15 SP2">
    <name>SUSE Package Hub 15 SP2 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP2-Backports-Pool</name>
        <summary>Package Hub 15 SP2</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  <group distversion="SUSE Linux Enterprise Server 15 SP3">
    <name>SUSE Package Hub 15 SP3 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP3-Backports-Pool</name>
        <summary>Package Hub 15 SP3</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  <group distversion="SUSE Linux Enterprise Desktop 15 SP3">
    <name>SUSE Package Hub 15 SP3 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP3-Backports-Pool</name>
        <summary>Package Hub 15 SP3</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  <group distversion="SUSE Linux Enterprise Server 15 SP4">
    <name>SUSE Package Hub 15 SP4 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP4-Backports-Pool</name>
        <summary>Package Hub 15 SP4</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  <group distversion="SUSE Linux Enterprise Desktop 15 SP4">
    <name>SUSE Package Hub 15 SP4 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP4-Backports-Pool</name>
        <summary>Package Hub 15 SP4</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  <group distversion="SUSE Linux Enterprise Server 15 SP5">
    <name>SUSE Package Hub 15 SP5 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP5-Standard-Pool</name>
        <summary>Package Hub 15 SP5</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  <group distversion="SUSE Linux Enterprise Desktop 15 SP5">
    <name>SUSE Package Hub 15 SP5 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP5-Standard-Pool</name>
        <summary>Package Hub 15 SP5</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  <group distversion="SUSE Linux Enterprise Server 15 SP6">
    <name>SUSE Package Hub 15 SP6 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP6-Standard-Pool</name>
        <summary>Package Hub 15 SP6</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  <group distversion="SUSE Linux Enterprise Desktop 15 SP6">
    <name>SUSE Package Hub 15 SP6 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP6-Standard-Pool</name>
        <summary>Package Hub 15 SP6</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  <group distversion="SUSE Linux Enterprise Server 15 SP7">
    <name>SUSE Package Hub 15 SP7 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP7-Standard-Pool</name>
        <summary>Package Hub 15 SP7</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  <group distversion="SUSE Linux Enterprise Desktop 15 SP7">
    <name>SUSE Package Hub 15 SP7 one-click install</name>
    <summary>Install perl-DateTime-Format-Mail</summary>
    <description>
    NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension

If the extension is not enabled, this installation will fail while trying to enable an invalid repo.

This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
    </description>
    <repositories>
      <repository recommended="true">
        <name>SUSE-PackageHub-15-SP7-Standard-Pool</name>
        <summary>Package Hub 15 SP7</summary>
        <description>Dummy repo - this will fail</description>
        <url></url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>perl-DateTime-Format-Mail</name>
        <summary>Convert between DateTime and RFC2822/822 formats</summary>
        <description>RFCs 2822 and 822 specify date formats to be used by email. This module
parses and emits such dates.

RFC2822 (April 2001) introduces a slightly different format of date than
that used by RFC822 (August 1982). The main correction is that the
preferred format is more limited, and thus easier to parse
programmatically.

Despite the ease of generating and parsing perfectly valid RFC822 and
RFC2822 people still get it wrong. So this module provides four things for
those handling mail dates:

* 1

A strict parser that will only accept RFC2822 dates, so you can see where
you&#x27;re right.

* 2

A strict formatter, so you can generate the right stuff to begin with.

* 3

A _loose_ parser, so you can take the misbegotten output from other
programs and turn it into something useful. This includes various minor
errors as well as some somewhat more bizarre mistakes. The file
_t/sample_dates_ in this module&#x27;s distribution should give you an idea of
what&#x27;s valid, while _t/invalid.t_ should do the same for what&#x27;s not. Those
regarded as invalid are just a bit *too* strange to allow.

* 4

Interoperation with the rest of the DateTime suite. These are a collection
of modules to handle dates in a modern and accurate fashion. In particular,
they make it trivial to parse, manipulate and then format dates. Shifting
timezones is a doddle, and converting between formats is a cinch.

As a future direction, I&#x27;m contemplating an even stricter parser that will
only accept dates with no obsolete elements.</description>
      </item>
    </software>
  </group>
  </metapackage>