You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Typically, runtime packages are loaded in path automatically, and sdk packages can be manually loaded in path for development environment like vscode. I suspect loading these packages in PATH will make them easier to find for opam.
Do the conf- packages in opam-repository need updating to work with flatpak-installed libraries (I’m assuming not?).
It’s not clear to me what you’re after - opam’s external dependency handling is for detecting that a given system package is installed and then driving the system package manager itself to install it if it’s not. So in the example given, it’s not that opam would be finding out where llvm-17 is, but querying whether the llvm-17 extension has been added.
I’m not at all familiar with Flatpak, but I think the support wanted in opam here might be similar to that needed for Nix? (cf. #5982)
Sorry, I completely misunderstood the purpose of depexts. I thought it is to find depexts, instead of installing depexts. Then I believe managing external dependency is not feasible for flatpak, because it would require a sandbox escape for the Ocaml SDK (i.e. permission to install other packages), which I am not sure is possible.
My issue is caused by installed the wrong version of llvm, so the ocaml library is not finding the installed version. After I installed the correct version, everything worked.
The location of packages in flatpak sdk is rather predicable. They are either in their location specified by the free desktop runtime or sdk.
See the following for runtime:
The other location packages can appear is sdk, where we can find them in
/usr/lib/sdk/${SDK_NAME}/
. For example, the llvm version 17 sdk:Typically, runtime packages are loaded in path automatically, and sdk packages can be manually loaded in path for development environment like vscode. I suspect loading these packages in PATH will make them easier to find for opam.
Additional Resources:
The text was updated successfully, but these errors were encountered: