Open joachimmetz opened 5 years ago
No releases in https://github.com/aff4/pyaff4 and 2017 release in https://pypi.org/project/PyAFF4/
Let's get this updated first, marking as blocked
Looks like this is going to be more involved:
Potential licensing issues:
New release 0.27 in PyPi.
Re the observation that the dependency list is going to be more involved, can you elaborate?
New release 0.27 in PyPi.
Thx
Re the observation that the dependency list is going to be more involved, can you elaborate?
The thing is that plaso ships a packaged version that includes all dependencies for this reason all dependencies need to be compatible with the plaso license (https://github.com/log2timeline/l2tdocs/blob/master/process/Dependencies.md). Seeing the uncertainty around compatibility of PD and FOSS (some context https://opensource.org/node/878) I would need to take a closer look how this affects plaso.
An option might be to make pyaff4 an optional dependency to dfVFS and not ship it as part of the packaged release of plaso. However this means additional steps in the release build process.
We could make the pyblake2 dependency a soft one - it isn't regularly used.
In general, the less dependencies the easier to deploy. Maybe an alternative approach is to have a pyaff4(-core) and pyaff4-blake (or equiv) split?
What is aff4-snappy, a fork from https://github.com/andrix/python-snappy? Under rekall-innovations (https://github.com/rekall-innovations/aff4-snappy)?
Asked for clarification: https://github.com/aff4/pyaff4/issues/9
To unblock https://github.com/log2timeline/dfvfs/issues/362 add PyAFF4 suppport to l2tdevtools and l2tbinaries/GIFT
https://pypi.org/project/PyAFF4/ https://github.com/aff4/pyaff4
@blschatz FYI
WIP: https://github.com/joachimmetz/l2tdevtools/tree/pyaff4