I've installed flatpak from git, because I am expecting to get an error related to my exported desktop file which the current 0.6.7 does not check for.
Anyway, I'm trying to use the new flatpak and flatpak-builder, so I call it from my prefix:
$ strace -f -eexecve /var/tmp/flatpak/bin/flatpak-builder --force-clean -v --repo=/tmp/fb.repo /tmp/fpbuilder org.gnome.Foo.json
...
Exporting org.gnome.Foo.Debug to repo
strace: Process 21629 attached
[pid 21629] execve("/home/muelli/.local/bin//flatpak", ["flatpak", "build-export", "--arch=x86_64", "--runtime", "--metadata=metadata.debuginfo", "--files=files/lib/debug", "/tmp/fb.repo", "/tmp/fpbuilder", "master"], [/* 66 vars */]) = -1 ENOENT (No such file or directory)
[pid 21629] execve("~/.local/bin/flatpak", ["flatpak", "build-export", "--arch=x86_64", "--runtime", "--metadata=metadata.debuginfo", "--files=files/lib/debug", "/tmp/fb.repo", "/tmp/fpbuilder", "master"], [/* 66 vars */]) = -1 ENOENT (No such file or directory)
[pid 21629] execve("$HOME/.local/bin/flatpak", ["flatpak", "build-export", "--arch=x86_64", "--runtime", "--metadata=metadata.debuginfo", "--files=files/lib/debug", "/tmp/fb.repo", "/tmp/fpbuilder", "master"], [/* 66 vars */]) = -1 ENOENT (No such file or directory)
[pid 21629] execve("/usr/local/sbin/flatpak", ["flatpak", "build-export", "--arch=x86_64", "--runtime", "--metadata=metadata.debuginfo", "--files=files/lib/debug", "/tmp/fb.repo", "/tmp/fpbuilder", "master"], [/* 66 vars */]) = -1 ENOENT (No such file or directory)
[pid 21629] execve("/usr/local/bin/flatpak", ["flatpak", "build-export", "--arch=x86_64", "--runtime", "--metadata=metadata.debuginfo", "--files=files/lib/debug", "/tmp/fb.repo", "/tmp/fpbuilder", "master"], [/* 66 vars */]) = -1 ENOENT (No such file or directory)
[pid 21629] execve("/usr/sbin/flatpak", ["flatpak", "build-export", "--arch=x86_64", "--runtime", "--metadata=metadata.debuginfo", "--files=files/lib/debug", "/tmp/fb.repo", "/tmp/fpbuilder", "master"], [/* 66 vars */]) = -1 ENOENT (No such file or directory)
[pid 21629] execve("/usr/bin/flatpak", ["flatpak", "build-export", "--arch=x86_64", "--runtime", "--metadata=metadata.debuginfo", "--files=files/lib/debug", "/tmp/fb.repo", "/tmp/fpbuilder", "master"], [/* 66 vars */]) = 0
...
I somehow expected it to call the newly installed flatpak binary. However, I see it trying to execute flatpak from various locations, e.g. ~/.local/bin
, but not relative to itself.
Now it might be a weird for the flatpak-builder binary to look for the "flatpak" binary relative to itself and I don't think I know anything that behaves similarly. But I somehow expected the new flatpak to be called. It would make my life a tiny bit easier if it did, because I wouldn't need to manipulate the PATH (which seems to be a little awkward to do in my shell, fish).
If calling the relative binary itself it too weird but looking for it is not, then a warning might be fruitful. Otherwise, feel free to close.