Hello Michael, Le samedi 09 octobre 2021 à 17:17 +0200, Michael Albinus a écrit : > > Guix system stores system-installed packages in > > > > "/run/current-system/profile/bin" "/run/current- > > system/profile/sbin" > > > > Unfortunately, getconf is unable to produce useful results on a > > Guix > > System server. > > > > In: > > > > https://guix.gnu.org/manual/devel/en/guix.html#operating_002dsystem-Reference > > > > you see that the system-installed packages [are] "installed in the > > global profile, which is accessible at /run/current- > > system/profile." > > > > Would you please add these paths to the default? > > It will be a pleasure for me to expand tramp-default-remote-path to > guix > specific paths. When "getconf PATH" doesn't work properly, we need > another indiciation for guix. What does "uname -sr" return on a guix > system? Or is there something else which helps us to determine a guix > system? Guix does not create /etc/os-release, and uname -sr returns "Linux <kernel version>" on my server. The most reliable thing would be to check if /run/current-system/configuration.scm exists (or .../provenance, or .../channels.scm):
https://guix.gnu.org/manual/devel/en/guix.html#provenance_002dservice_002dtype This service (that creates these files) is enabled by default, but it can be turned off (so, maybe the files are missing but the system programs are still in /run/current-system/profile/). However, it should be very commonly enabled. Is it not possible to just test for the existence of the /run/current- system/profile/bin (and .../sbin if needed) directory? I’m not familiar with the tramp code base, why should tramp even know it is connecting to a guix system server? I thought it would just set the PATH to all possible default candidates and let the remote shell decide. Is it not the case? Vivien
