Prj2 #405
Prj2 #405
Conversation
|
|
||
| **Persistent Across Sessions:** | ||
|
|
||
| Annotations are stored globally in the `~/.local/share/radare2/cache` directory. This ensures that they are accessible across different sessions, even if the project is closed and reopened later. |
There was a problem hiding this comment.
Is this somehow configurable/overridable? I'd like to self-contain my project metadata in my own location... if I change between computers I want to have that metadata available on the git repository of MY project.
There was a problem hiding this comment.
|
|
||
| First of all we will create a directory to contain the binar(y/ies) you want to work on. Then you can create a **Makefile** or a shellscript with the commands to run like this: | ||
| This workflow demands consistency and discipline from the user. It’s crucial to maintain an organized system to ensure that important metadata isn’t lost, as nothing is auto-saved unless explicitly written into the project script by the user. |
There was a problem hiding this comment.
Why not? Can't there just be a configurable timer that auto-saves? As a user I don't want to be consistent with auto-backups, even Emacs does that :P :P
|
|
||
| Radare2 also provides a mechanism for users to define actions that are performed when leaving the shell. The `cmd.exit` configuration variable can be set to run specific commands or scripts when the session ends. For example, you could create a `.r2.js` script that saves all comments and function names before closing the session. | ||
|
|
||
| However, it’s important to remember that it’s up to the user to manage and manually update project scripts with new flags, analysis commands, or comments. While this approach requires more effort, it offers unmatched flexibility. |
There was a problem hiding this comment.
Sure, but a timer-based auto-save MUST be provided as well, IMHO.
|
|
||
| Radare2 have its own versioning control system. It's like a simple `git`. But also acts as a way to wrap the use of **git** under the same API. | ||
| Radare2 includes a built-in version control system that operates similarly to Git, offering project versioning under the command `ravc2` (or its API counterpart, `rvc`). This allows users to manage their project history, track changes, revert to previous versions, and more. Radare2's project versioning system integrates seamlessly with Git, allowing you to choose between Radare2's versioning system or wrapping Git under the same interface. |
There was a problem hiding this comment.
Still very unclear WHY would I choose rvc over git... totally understand why one would use version control, but it's not clear at all (to me) wht your custom version control system would be preferable against git.
|
|
||
| ### Conclusion | ||
|
|
||
| Radare2's versioning system with `ravc2` allows for efficient project management, enabling users to track progress, collaborate, and ensure that their analysis history is well-documented. Whether you use `rvc` or integrate with Git, version control in Radare2 provides flexibility and powerful tools for maintaining analysis continuity. |
There was a problem hiding this comment.
This reads as a generic non-conclusion? Explains how ravc2 works but not how it really benefits the user in any substantial way versus git?
Checklist
Description