pkgsrc VS binary-parsing

It's a bit overkill for only building Poke, but you can use Pkgsrc [1] to do so on macOS:

Bootstrap Pkgsrc:

git clone https://github.com/NetBSD/pkgsrc.git

Looking at pkgsrc/sysutils/libvirt/PLIST it doesn't look like the package provides any Python bindings -- which is what the "ImportError: No module named libvirt" error message is about. You could try py-libvirt from pkgsrc-wip and see how that works out.

The repository of record is CVS, but you can - like many of us do - use either the HG export (https://anonhg.netbsd.org/pkgsrc) or GitHub (https://github.com/netbsd/pkgsrc) instead.

At some point we will transition the repository of record to something else, but it's being done carefully. We want to do it right, and there aren't many volunteers willing help with the work.

it's worth noting that there were some ppc-specific commits to ffmpeg4 since: 1, 2

* binary-parsing - https://github.com/dloss/binary-parsing

There are a few hex/disk editors that support "templates" (but you need most times to create those yourself).

Here is a sort of "curated list" of related tools:

https://github.com/dloss/binary-parsing

The most complete/populated I know of is Kaitai:

http://kaitai.io/

http://formats.kaitai.io/

that you can use with Hiew with Kiewtai

https://github.com/taviso/kiewtai

If the question is slightly different, i.e. which bytes are used to identify a given file format, there is Trid:

https://mark0.net/soft-trid-e.html

Which has also a database of known headers/patterns.

Nice! Some other tools and parsers: https://github.com/dloss/binary-parsing