Shell integration plugins have dependency on client in distro packaging

[fmoc]

Follow-up from #8967 (comment).

@TheOneRing reports that distro provided Dolphin plugin packages have a superfluous dependency on the client package. It should at most be a recommendation or suggestion.

To add some context: the shell integration plugins hardly ever change, as they pull information like the menu entries they shall generate from the client. A years-old shell integration plugin can work just fine with an up-to-date AppImage for instance.
As we cannot easily ship the shell integration in AppImages (especially the Dolphin plugin is troublesome), we consider recommending users to install the distro packages until there is a solution. It makes no sense to require them to install an old client in such a scenario. And the client is not a strict dependency (the plugin can be installed just fine without the client, it won't do anything useful but it does not cause issues). Therefore, the relation between the two packages should be relaxed.

[fmoc]

Debian depends on the client package: https://packages.debian.org/buster/dolphin-owncloud
Same goes for Ubuntu: https://packages.ubuntu.com/focal/dolphin-owncloud

I've been looking a bit for similar packages in RPM-based distros, but I can't find such packages for CentOS/Fedora or openSUSE, for instance. I suppose they package the shell integration within the main client package?

[TheOneRing]

Debian depends on the client package: https://packages.debian.org/buster/dolphin-owncloud
Same goes for Ubuntu: https://packages.ubuntu.com/focal/dolphin-owncloud

I've been looking a bit for similar packages in RPM-based distros, but I can't find such packages for CentOS/Fedora or openSUSE, for instance. I suppose they package the shell integration within the main client package?

@dragotin you can fill in the suse part :D

[github-actions]

This issue was marked stale because it has been open for 30 days with no activity. Remove the stale label or comment or this will be closed in 7 days.

[fmoc]

I asked the Debian maintainers to remove the hard dependency on the client platform on the mailing list.

[fmoc]

Our installation script skips the known incompatible Debian/Ubuntu packages: https://github.com/owncloud/client-desktop-install-shell-integration/blob/487024717f00275ab99a17e1cba7848069614d0e/install-extensions.sh#L183-L191

[TheOneRing]

The current script does not install the shell extensions on one of the biggest distros out there.
In my opinion there is no harm in installing the outdated client, as long as we describe why we do it, and that the user should only use the Appimage and not the outdated 2.5 client.

[fmoc]

This doesn't accurately describe the situation. The script does install shell extensions, but it refuses to install the downstream Debian packages. It will, however, install our upstream packages.

I don't really have a preference. I can relate to the argument that it'd be confusing to have more than one ownCloud menu entry around...

[dragotin]

Sorry for being late to the party. This is the source of the openSUSE package, just for reference:
https://build.opensuse.org/package/show/KDE:Extra/owncloud-client

From there it is semi-automatically pulled into the openSUSE Tumbleweed distro and later into the released versions like Leap 15.4.

The current package also has a hard dep from owncloud-client-dolphin to the main client package.

I can package the dolphin plugin completely independent if we have separate sources (a real tarball I mean). If not, it is probably better to leave it with the main package, but just remove the dependency.