How to use Pixi on pCloud Drive etc. (which ignores symlinks)?

[mforbes]

I was trying to show how useful pixi is to a colleague, who was creating a project on a remote drive managed by pCloud Drive. The result was the following, which was rather unhelpful:

$ RUST_BACKTRACE=1 pixi add python
⠉ preparing packages   [╾───────────────────]  2/13 python (+8) @ 0B/s
⠉ installing           [────────────────────]  0/22 _openmp_mutex (+6)
thread 'tokio-runtime-worker' panicked at
crates/pixi_reporters/src/[download_verify_reporter.rs:231](http://download_verify_reporter.rs:231/):14:
entry is missing from tracker
stack backtrace:
Error:   × failed to link _openmp_mutex-4.5-2_gnu.tar.bz2
  ├─▶ failed to link 'lib/[libgomp.so](http://libgomp.so/).1'
  ├─▶ failed to copy file to destination
  ╰─▶ failed to copy file from
~/.cache/rattler/cache/pkgs/_openmp_mutex-4.5-2_gnu/lib/[libgomp.so](http://libgomp.so/).1
to ~/pCloudDrive/Project/.pixi/envs/default/lib/[libgomp.so](http://libgomp.so/).1: No such file or directory
(os error 2)

I gather than pCloudDrive does not support symlinks, and that this is the issue. (The failure to link etc.)

Is there any way to improve the user experience so that it is clear from the reporting that the issue is related to the remote drive and not something else? (Searching for related issues hints at file corruption from network issues etc. which are not relevant.)

There are some relevant issues like #997 which led to #1381 and detached-environments, but there really does not seem to be any discussion about the potential issues in the docs.

Just looking for some suggestions/feedback before opening an issue in case I missed something. Not sure if this should just be a documentation fix, or if there could be some improved error reporting.