If not installed, when trying to access the remote device via 'Remote filesystem browser', you get nothing but an error message (which might not be clear for every user immediately). I think there are two options, 1) add it to RDEPEND even though using the plugin still is completely optional, or 2) document it in pkg_postinst(). A patch for 2) could look like this: --- a/kdeconnect-9999.ebuild 2013-10-30 22:57:21.947649046 +0100 +++ b/kdeconnect-9999.ebuild 2014-03-09 22:31:34.372716701 +0100 @@ -41,8 +41,10 @@ } pkg_postinst(){ - einfo - einfo "The Android .apk file is available via" - einfo "https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp" - einfo + elog "Optional dependencies:" + elog " sys-fs/sshfs-fuse (for 'Remote filesystem browser' plugin)" + elog + elog "The Android .apk file is available via" + elog "https://play.google.com/store/apps/details?id=org.kde.kdeconnect_tp" + elog }
*kdeconnect-0.5.1 (11 Mar 2014) 11 Mar 2014; Manuel Rüger <mrueg@gentoo.org> +kdeconnect-0.5.1.ebuild, -kdeconnect-0.5.ebuild: Version bump. Add info about optional rdep: sshfs-fuse. Thanks to Andreas Sturmlechner. Fixes bug #504022
Why would you not add the fuse USE flag as per x2goserver? http://gpo.zugaina.org/AJAX/Ebuild/2607611/View That said I have installed 0.5.1 alongside sshfs-fuse on kde-4.12.3 and when trying to browse my Samsung Galaxy S11 via konqueror, I get "Unsupported Protocol kdeconnect" Should I file a new bug or is file browsing not supported in kdeconnect-0.5.1(as suggested by the android app)? If the latter, I would think the post install message is not needed for this version?
It seems they indeed comment it out for each stable release so far: https://projects.kde.org/projects/playground/base/kdeconnect-kde/repository/revisions/fb4441c740d2b9f0299489432518abe6d8e966c7 Maybe someone should donate them a config switch. ;) @barrie: Optional runtime deps are an unsolved topic so far: see bug 453618
*** Bug 631830 has been marked as a duplicate of this bug. ***
