angr-vex's library is dlopen(3)ed py py-pyvex (not py-angr itself), so
register it as proper RDEP in py-pyvex (and only there).
Spotted after `pkg_add angrop' on a fresh installation where angr-vex was
not installed; even though angr has an LDEP on it, our framework does not
turn it into a RDEP unless angr also links against it.
vex is amd64-only and there is no point in attempting to build packages
only to have them fail when the RDEP on vex cannot be resolved (e.g. on
i386 as reported by sthen).
prompted by sthen@
ok kn@
angr is a suite of Python 3 libraries that let you load a binary
and do a lot of cool things to it:
- Disassembly and intermediate-representation lifting
- Program instrumentation
- Symbolic execution
- Control-flow analysis
- Data-dependency analysis
- Value-set analysis (VSA)
- Decompilation
join work with and ok kn@
rough edges will be handled in-tree