Who decide package names? (sshfs vs fs-sshfs)

Hello

Trying to install KDE-services (kde-services-1.9-6.fc20.noarch) addon for Dolphin on KDE, I was not able to do, cause a dependency, “fuse-sshfs”, was not available. After looking at package search service, I found a lot of “fuse-???” packages, FUSE related, and other like “ruby-fuse…”, “python-fuse…”. So I decided to look for “sshfs” and “voilá”, that’s the package name of “fuse-sshfs” under OpenSUSE repositories. Result: Only distros that called “fuse-sshfs” to that package can install KDE-Services under KDE. I think, and I’m sure you will too, that is more “intuitive” (I will avoid talk about “logic”) to name the package “fuse-sshfs”, so why to complicate easy things? Is there any solution? Am I wrong?

Thank you and best regards

On 2014-05-22 11:26, faleloncio wrote:
>
> Hello
>
> Trying to install KDE-services (kde-services-1.9-6.fc20.noarch) addon
> for Dolphin on KDE, I was not able to do, cause a dependency,
> “fuse-sshfs”, was not available. After looking at package search
> service, I found a lot of “fuse-???” packages, FUSE related, and other
> like “ruby-fuse…”, “python-fuse…”. So I decided to look for “sshfs”
> and “voilá”, that’s the package name of “fuse-sshfs” under OpenSUSE
> repositories. I think, and I’m sure you will too, that is more
> “intuitive” (I will avoid talk about “logic”) to name the package
> “fuse-sshfs”, so why to complicate easy things?

Each distribution names packages as they seem fit.

And I guess that the KDE-services thing you were installing was not an
openSUSE package.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))