Skip to content

Handle version upgrades #8

@XVilka

Description

@XVilka

For example, if you had Rizin version 0.1.0 but just upgraded to 0.2.0 all installed plugins will show the following error:

rizin on  dev [$] 
[i] ℤ rizin /bin/ls                                                                                                                                                                                                               18:10:04 
Module version mismatch /home/user/.local/share/rizin/plugins/core_ghidra.so (0.1.0-git) vs (0.2.0-git)
Module version mismatch /home/user/.local/share/rizin/plugins/asm_ghidra.so (0.1.0-git) vs (0.2.0-git)
Module version mismatch /home/user/.local/share/rizin/plugins/analysis_ghidra.so (0.1.0-git) vs (0.2.0-git)
Module version mismatch /home/user/.local/share/rizin/plugins/core_pdd.so (0.1.0-git) vs (0.2.0-git)
Warning: run rizin with -e io.cache=true to fix relocations in disassembly
 -- The more 'a' you add after 'aa' the more analysis steps are executed.
[0x00006b60]> q
rizin on  dev [$] took 6s 

Both rz-pm and rizin (by calling rz-pm as a command or using integration through the API #2) should handle this situation in a more user-friendly way, suggesting the user to update those plugins or in any similar fashion.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions