Repository navigation
[Feature Request] check the profile and dependent package information from established ruyi virtual environment #379
Description
ruyi version: 0.42.0
Currently, we can obtain dependent profile information from the established ruyi virtual environment:
$ cat ruyi-venv.toml
[config]
profile = "generic"
sysroot = "/home/user/venv/sysroot.riscv64-plct-linux-gnu"
$ cat ruyi-cache.v2.toml
# NOTE: This file is managed by ruyi. DO NOT EDIT!
[cached_v2]
[cached_v2.targets.riscv64-plct-linux-gnu]
toolchain_bindir = "/home/user/.local/share/ruyi/binaries/x86_64/gnu-plct-0.20250912.0/bin"
toolchain_flags = "-march=rv64gc -mabi=lp64d"
toolchain_sysroot = "/home/user/venv/sysroot.riscv64-plct-linux-gnu"
[cached_v2.cmd_metadata_map."riscv64-plct-linux-gnu-gcc"]
dest = "/home/user/.local/share/ruyi/binaries/x86_64/gnu-plct-0.20250912.0/bin/riscv64-plct-linux-gnu-gcc"
......
Although the toolchain installation directory can be obtained from toolchain_bindir, the dependent toolchain name and version cannot be obtained directly.
In addition, when a profile configuration in packages-index is different from the configuration with the same name in the virtual environment, ruyi may also need to prompt for relevant changes.
These features may facilitate the use of IDEs to manage virtual environments. The details of these features may require further discussion.
Activity
feat(venv): include PM metadata in created venv
feat(venv): include PM metadata in created venv