Bug 1524756

Summary:	plasma-discover-flatpak-backend should add flathub repo during installation
Product:	[Fedora] Fedora	Reporter:	Nate Graham <nate>
Component:	plasma-discover	Assignee:	marcdeop
Status:	ASSIGNED ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	jgrulich, kde-sig, ngompa13, postix, rdieter
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nate Graham 2017-12-12 00:31:24 UTC

The plasma-discover-flatpak-backend package isn't very useful without any repos configured. Right now, Flathub is the only really useful one, so I think it makes sense to add it when the package is installed, to save the user (who is probably non-technical if they want to use the Flatpak backend) from having to figure out that they have to add a Flatpak repo, what one would be, how to do it, etc.

I recommended doing this automatically for all distros in https://bugs.kde.org/show_bug.cgi?id=387718, but Discover's author and maintainer advised that this is a distro packager's decision. So here I am, asking Fedora's plasma-discover packagers to automatically add the Flathub repo (https://flathub.org/repo/flathub.flatpakrepo) when plasma-discover-flatpak-backend is installed. :)

Comment 1 Fedora End Of Life 2018-02-20 15:25:58 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 2 Rex Dieter 2018-06-01 17:24:13 UTC

One question is how best to implement that (it is a shame upstream poo poo'd doing it by default).

Comment 3 Nate Graham 2018-06-03 22:23:14 UTC

Probably the simplest approach would be to add a shell script command in the packaging that gets run as the very last step of installing the Flatpak backend package is installed:

flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

Comment 4 Nate Graham 2020-11-03 16:13:45 UTC

FWIW Neon does this by shipping a systemd unit that runs a small script:

https://invent.kde.org/neon/neon/settings/-/blob/Neon/unstable/debian/neon-settings-2.neon-flathub.service
https://invent.kde.org/neon/neon/settings/-/blob/Neon/unstable/usr/lib/neon_update/neon_flathub.rb

Comment 5 Neal Gompa 2020-11-03 16:17:07 UTC

This is currently blocked on creating a filtered flathub view that passes policy and legal qualification. That is driven by the Workstation WG currently.

Comment 6 Fedora Admin user for bugzilla script actions 2025-07-17 01:12:00 UTC

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.