Shippign kio-fuse by default

Martin Steigerwald martin at lichtvoll.de
Thu Feb 4 09:22:20 GMT 2021


Pino Toscano - 03.02.21, 23:11:41 CET:
> In data mercoledì 3 febbraio 2021 11:27:37 CET, Aurélien COUDERC ha 
> scritto:
> > upstream advised [1] that we ship kio-fuse by default as it gives a
> > nice improvement in the use of non-kde apps.
> 
> TBH: Nate sometimes tends to be a little bit too pushy for stuff he
> cares about. kio-fuse had its first (and to this day only) release
> barely a couple of months ago, so installing it by default without
> a bit more of testing does not seem like one of the best ideas, IMHO.

I could test it a bit. However, I did not yet fully understand how to 
trigger its usage. See below.

> > Can I make it a recommends of kio ?
> 
> kio is pulled mostly by applications using kio, which means that they
> are using kio-slaves already, and thus kio-fuse is useless for them.
> Not to mention that

that what?
 
> > Any other/better idea ?
> 
> At most a recommend of kde-standard. For the reasons above, I'd be
> more included for a suggest only (which means not installed by
> default).

In order to have an opinion on that I'd like to know how it actually is 
triggered. I thought opening a directory with for example FISH kio slave 
in Dolphin would not yet trigger it, cause Dolphin is KIO aware. But I 
also thought that when I tell Dolphin to open a file from such a 
directory with a non kio-slave aware application it would do the FUSE 
thing. Yet here, despite kio-fuse installed, running as process and 
despite its DBUS interface being available, the application does not 
open the file. Also I see no FUSE mount.

If kio-fuse is only triggered if specifically asked to by an user in some 
way I'd say a recommend would be fine enough. At least here it does not 
seem to replace KIO slaves in KIO slave aware applications – I wonder 
whether upstream will replace that slave terminology… so the possible 
impact of recommending it in kde-standard may be quite low.

I will ask upstream how to actually trigger and use KIO fuse as it at 
the moment is not immediately obvious to me.

Best,
-- 
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20210204/0e872454/attachment.sig>


More information about the pkg-kde-talk mailing list