Mark todo and skip fromtcpdump tests

Net::DNS::Packet doesn't serialize properly yet.  JSON::XS is configured
to allow blessed objects and convert them if a TO_JSON method is
available.  If TO_JSON is not available, however, the object is replaced
by a JSON null.  Net::DNS::Packet doesn't have a TO_JSON method.
Monkey-patching one in will require futzing with a number of other
classes contained with Net::DNS::Packet objects too.

See GH #32.
Standardize POD width at 80 chars to avoid fluctuation
Regenerate POD to pickup new doc
MYMETA.* don't belong in the shipped tarball

They are explicitly per-Makefile.PL invocation files specific to the
environment.
Update MANIFEST
Text::CSV_XS 0.98 under Perl 5.18.1 causes test failures; require 0.99

The most telling failure is in fromcsv.t, while parsing this:

    foo,bar,baz
    "foo
    loo","bar loo", baz

resulting in:

    Expected:
    {"zip":["foo","bar","baz"]}
    {"zip":["foo\nloo","bar loo","baz"]}
    Output from module:
    {"zip":["foo","bar","baz"]}
    {"zip":["\"foo"]}
    {"zip":["loo\"","bar loo","baz"]}

The same parsing bug caused failures in FilenameKey.t as well.
Merge pull request #33 from tsibley/skip-fromtcpdump-tests

Mark todo and skip fromtcpdump tests
Merge pull request #34 from tsibley/fixed-pod-width

Fixed pod width
Merge pull request #35 from tsibley/update-manifest

Update manifest
Merge pull request #36 from tsibley/csv-dep-on-5.18

Text::CSV_XS 0.98 under Perl 5.18.1 causes test failures; require 0.99
Sort hash keys when generating help so the order doesn't change run to run on 5.18
MANIFEST belongs in itself

Otherwise the MANIFEST isn't included in the dist for double-checking
dist contents.
Bump version to 3.7.4 and update Changes
Bump release version to 3.7.5 and change package versions to just "3.7"

The previous release version, 3.7.4, is represented as 3.007004 in the
style of Perl itself.  In the 3.7.3 release, the individual package
versions (not the release version) were 3.4.  3.4.0 would have expanded
into 3.004000, which is smaller than 3.007004, but 3.4 remains 3.4 and
is larger than 3.007004.  PAUSE doesn't like the decreasing version
numbers (for good reason) and so won't index it.

By changing the package versions back to just 3.7, this new release as
3.7.5 will be indexed by PAUSE.  New release versions with the same
module versions should still be indexed properly.

In general I prefer to keep the module versions the same as the release
version, but we won't be able to unless we force reset the existing
individual module versions (3.4 but soon 3.7) in PAUSE and we upload a
new release with module versions of the style "x.y.z". This is generally
considered the nuclear option though, and may make it hard for anyone
with an earlier version from CPAN to upgrade unless they know about the
newer versions.
A small script to update all module versions
Bump all versions to 4.0.0 to get out from under 3.7 vs. 3.00700x silliness

From now on, module version numbers should be x.y.z and ideally match
the release (tarball) version.

The release version matching the module versions ensures that new
releases will not be invisible to CPAN clients, which only look at
module versions.
Extract release version from the primary module

One less place to update.
Release 4.0.1 with Changes for 4.0.0 (and 4.0.1)

I forgot to include a Changelog for 4.0.0, so 4.0.1 corrects this.
Luckily version numbers are cheap!
fix DomainLanguage.t comparison on perls compiled with longdouble
Merge pull request #37 from elindsey/longdouble_tests

fix DomainLanguage.t comparison on perls compiled with longdouble