I never understood why the handling of these mounts is done on the KDE level, it never made sense to me and the issues with it were obvious since day one
Why not make this a separate service that has no KDE requirements but that KDE can use to get these mounts done? This way it can work with everything
The handling of the mount is not done at the KDE level, that's just where it's surfaced. smbclient already has no KDE deps, you can use mount and put them in /etc/fstab. It really looks like it has nothing to do with KDE to me (as a Plasma user)
I never understood why the handling of these mounts is done on the KDE level, it never made sense to me and the issues with it were obvious since day one
Why not make this a separate service that has no KDE requirements but that KDE can use to get these mounts done? This way it can work with everything
The handling of the mount is not done at the KDE level, that's just where it's surfaced.
smbclientalready has no KDE deps, you can usemountand put them in/etc/fstab. It really looks like it has nothing to do with KDE to me (as a Plasma user)It does in that in dolphin, it'll use mtp:// for example, and good luck finding out where the hell that is mounted. Hint: it's not in /mnt or /media
Multiple desktop environments and other pieces of software support SMB mounts. Many of them probably use the same library to do it.
Maybe, but why not have it mount the Linux way in the filesystem so that everything can access it without having to use these libraries?
This feels more like a microsoft solution
That's... the only way to do it?