Create metapackages for common dependencies #673
Labels
🌀 COMMANDO-VM
A package or future to be used by COMMANDO VM
🌀 FLARE-VM
A package or feature to be used by FLARE-VM
❔ discussion
Further discussion is needed
🆕 package
New package request/idea/PR
Milestone
Installing several versions of the same software can be an issue (see for example: #622). That's why I think we should have metapackages for at least the several tools. This will make it easier in the future to keep them in sync.
python3.vm
We are currently using python
[3.10.0, 3.11.0)
in libraries.python3.vm, ida.plugin.capa.vm and didier-stevens-suite.vm.openjdk.vm
We are currently using the open source openjdk in ghidra.vm and dex2jar.vm while we use javaruntime (last version of Java Oracle with a commercial license) in bytecodeviewer.vm. I propose we use a openjdk metapackage for all of them.
I think the only issue is that we need a workaround to open jar files by default.
At the moment we are using openjdk version
[21.0.0]
, but I think we should update it to[21.0.0, 21.1.0)
to prevent automatic updates. Only the metapackage will be tested when the dependency is updated. But even without the metapackage we are not testing that tools keep working in the CI only that they install successfully.nodejs.vm
malware-jail.vm and pkg-unpacker (in #670) use nodejs version
[20.7.0]
. I propose to update to[20.7.0, 20.8.0)
to prevent automatic updates for the reasons mention above.@mandiant/flare-vm opinions? any other tools we should move to a metapackage?
The text was updated successfully, but these errors were encountered: