https://bugs.kde.org/show_bug.cgi?id=422090
--- Comment #1 from Fabian Vogt <fab...@ritter-vogt.de> --- Git commit 1fedbb198f9cf785108babc673d377dc169a745e by Fabian Vogt. Committed on 01/08/2020 at 12:53. Pushed by fvogt into branch 'master'. Reimplement mounting in a different way Instead of always creating an origin node at the authority level and creating all path elements as directories, only create everything up to the origin when mounting. Everything beyond that is created on-demand when an application triggers readdir or lookup. Some ioslaves like tar don't support access at the root level (tar:/// doesn't exist), so for mounting those it has to traverse the URL upward until a valid origin is found. As mountUrl no longer creates all nodes to resolve the full URL, it returns a string in the callback now instead of a node. As there is no longer a concept of a protocol node, it was replaced with a plain DirNode instead. remoteUrl had to be fixed to deal with m_overrideUrl having a non-empty (or '/') path, it didn't add '/' before. The algorithm of localPathToRemoteUrl was changed to not need all path elements as nodes. It stops traversing once an origin was found. This means it behaves incorrectly/unexpectedly with nested origins. Related: bug 422091 M +34 -2 DESIGN M +2 -2 kiofuseservice.cpp M +194 -170 kiofusevfs.cpp M +9 -4 kiofusevfs.h M +1 -9 tests/fileopstest.cpp https://invent.kde.org/system/kio-fuse/commit/1fedbb198f9cf785108babc673d377dc169a745e -- You are receiving this mail because: You are watching all bug changes.
