Hi,

updating plaso is a mess due to its number of dependencies, luckily the
versions are all >= which makes it kind of easier.

due to the sheer number of new dependencies, and updated dependencies,
sending them here in one go, the tarball with the new deps, and the patch
with the updated dependencies as well as plaso update.


Updating plaso to latest, will add 14 new dependencies, those are in
new_plaso_deps.tar.gz. Especially all those libXXXX dependencies are from
github/libyal, similar to the majority of the existing dependencies.
Therefore they follow the same scheme. They all have a problem with 'make
test', python module loading fails.  But that seem to be systematic problem
for all of them, and not new, as it was with the same with the existing
libyal ports, and their updates. Running 'make test' in plaso, just works
for all but one test.

Then there are a 3 new py-* dependencies.

The update of plaso, and the existing dependencies (all in all 31 ports)
are very mechanical. Updating version number, take MAINTAINER, and change
the --enable-python3 -> --enable-python configure parameter. All libXXXX
minor SHLIB bump, and some with updated WANTLIB.
As said above, make test in plaso works for all, but one.
I would like to look at the failed library test, and that failing plaso
test, once it's all in.

Other than that, test reports, comments etc. welcome.

cheers,
Sebastian

• new_plaso_deps.tar.gz (13K)
• plaso_and_deps_updates.diff (321K)