[Discover] [Bug 388921] Can't choose which Flatpak repo is default when more than one are active

[Aleix Pol]

https://bugs.kde.org/show_bug.cgi?id=388921

Aleix Pol  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/dis
   ||cover/0f823c0bed40cbbe59cad
   ||7edc1caf424483c10c3
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from Aleix Pol  ---
Git commit 0f823c0bed40cbbe59cad7edc1caf424483c10c3 by Aleix Pol.
Committed on 04/05/2018 at 15:15.
Pushed by apol into branch 'master'.

Make it possible to choose which is the favorite flatpak source

Includes controls to raise and lower the preference of the different
flatpak backends available.

M  +1-0discover/DiscoverObject.cpp
M  +21   -1discover/qml/SourcesPage.qml
M  +14   -0libdiscover/backends/DummyBackend/DummySourcesBackend.cpp
M  +3-0libdiscover/backends/DummyBackend/DummySourcesBackend.h
M  +2-1libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp
M  +65   -2libdiscover/backends/FlatpakBackend/FlatpakSourcesBackend.cpp
M  +8-0libdiscover/backends/FlatpakBackend/FlatpakSourcesBackend.h
M  +20   -0libdiscover/resources/AbstractSourcesBackend.cpp
M  +11   -0libdiscover/resources/AbstractSourcesBackend.h

https://commits.kde.org/discover/0f823c0bed40cbbe59cad7edc1caf424483c10c3

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 388921] Can't choose which Flatpak repo is default when more than one are active

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=388921

--- Comment #9 from Nate Graham  ---
This bug isn't about which repository within a backend is the default, but
rather how the user can choose which one it is.

Internally, what I think makes the most sense is to keep the first repository
that's added as the default until the user deliberately changes it. We don't
want the default changing out from under the user; that would be weird and
jarring.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 388921] Can't choose which Flatpak repo is default when more than one are active

[Aleix Pol]

https://bugs.kde.org/show_bug.cgi?id=388921

--- Comment #8 from Aleix Pol  ---
Then you'll change back again?

Another metric could be to default to the repository that has the most
applications installed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 388921] Can't choose which Flatpak repo is default when more than one are active

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=388921

--- Comment #7 from Nate Graham  ---
Then if you install Flathub and KDEapps, it will default to KDEapps, which
probably isn't what you want.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 388921] Can't choose which Flatpak repo is default when more than one are active

[Aleix Pol]

https://bugs.kde.org/show_bug.cgi?id=388921

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #6 from Aleix Pol  ---
How about we default internally within Discover to whichever repository was
last installed? This way we don't really have to add weird UI anyway to
configure it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 388921] Can't choose which Flatpak repo is default when more than one are active

[Thomas Pfeiffer]

https://bugs.kde.org/show_bug.cgi?id=388921

Thomas Pfeiffer  changed:

   What|Removed |Added

 CC||thomas.pfeif...@kde.org

--- Comment #5 from Thomas Pfeiffer  ---
Suggestion: Have a top-level entry for each package provider, for example

Distribution packages (or ideally the distro's name) 
KDE Flatpak
Flathub
Ubuntu Store (or whatever they call their snap repos)

And then have the different repos/channels of the same provider on a second
level. Because for a user, who the package comes from is more important than
the format it's in

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 388921] Can't choose which Flatpak repo is default when more than one are active

[Aleix Pol]

https://bugs.kde.org/show_bug.cgi?id=388921

--- Comment #4 from Aleix Pol  ---
That would make it hairier, because then we'd get to: I want it from snap
otherwise the PPA and fallback to the distro.

Priorities within sources could make sense.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 388921] Can't choose which Flatpak repo is default when more than one are active

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=388921

--- Comment #3 from Nate Graham  ---
Maybe the default chooser UI should apply to repos and not sources? That could
get hairy since most distros are provisioned with multiple repos, though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 388921] Can't choose which Flatpak repo is default when more than one are active

[Aleix Pol]

https://bugs.kde.org/show_bug.cgi?id=388921

--- Comment #2 from Aleix Pol  ---
Yes, I'm not sure what's the best UI there. It's more like we should be able to
sort the sources by preference. i.e. having 1 main source doesn't really solve
it because we can have an application that is available on several sources,
just not on the main one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 388921] Can't choose which Flatpak repo is default when more than one are active

[Dr . Chapatin]

https://bugs.kde.org/show_bug.cgi?id=388921

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 388921] Can't choose which Flatpak repo is default when more than one are active

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=388921

--- Comment #1 from Nate Graham  ---
Created attachment 109843
  --> https://bugs.kde.org/attachment.cgi?id=109843=edit
Multiple Flatpak sources with flathub listed first, implying (erroneously) that
it is the default Flatpak source

-- 
You are receiving this mail because:
You are watching all bug changes.