After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 745277 - Missing applications in installed view when a single package provide multiple applications
Missing applications in installed view when a single package provide multiple...
Status: RESOLVED NOTGNOME
Product: gnome-software
Classification: Applications
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Software maintainer(s)
GNOME Software maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-02-27 10:01 UTC by Fabien Bourigault
Modified: 2015-09-20 11:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Fabien Bourigault 2015-02-27 10:01:12 UTC
In Arch Linux there is no split (or few) split packages, so many packages provides more than one *.desktop file that is an application. In the installed view, only one application per package is displayed.

Regards,
Fabien
Comment 1 Fabien Bourigault 2015-02-27 10:05:01 UTC
Original bug description by brittyazel on Arch Linux bbs : https://bbs.archlinux.org/viewtopic.php?pid=1506535#p1506535
Comment 2 Matthias Clasen 2015-02-27 22:09:02 UTC
The assumptions that applications can be individually installed and removed is pretty fundamental to the design of gnome-software.
Comment 3 Fabien Bourigault 2015-02-27 23:54:49 UTC
Is it possible to have a single package displaying once for each application and while removing an app having a popup to tell user it will also remove the other apps provided by the package? This will solve the Arch Linux issue and IMHO will not happend on fedora.
Comment 4 Matthias Clasen 2015-02-28 19:12:42 UTC
I think it would be much better to fix the packaging to be application-centric, if you want to use an application installer.
Comment 5 Britt Yazel 2015-03-05 19:50:34 UTC
I agree that it is a better solution to have packages be application-centric; however, I do not think this is a realistic expectation that Archlinux as a whole will make. I proposed that a single package be split into a one application per package paradigm, but it was fairly immediately shot down.

So, unfortunate as it is, it seems that this solution may have to be one the gnome-software side of things. Further, I just got word this morning that Muon added support for detecting and dealing with multiple .desktop files per package.


Is this a future you think gnome-software could be persuaded to go towards? I greatly hope so, as it could be of great use not only for organizing installed apps into respective app-folders, but also in showing applications to be installed that are hosted within another package (and that otherwise would not show up in a search, I.E. Qt-designer hosted within the Qt4 package).
Comment 6 Fabien Bourigault 2015-03-05 20:54:17 UTC
I'm writing a tool to get packageing errors. At a first look there is not so many errors and I looked at the qt4 bug report you did on Arch Linux bug tracker and the comment in the duplicate issue is that it's too hard to split the package because upstream don't care. I know other distro did the split but to fit the KISS philosophy is to contribute upstream to make the split easier.

As you can see the qt5 package have tools in a separate package because upstream make it possible.

So we will need to contribute upstream to make the split easier.
Comment 7 Alexandre Franke 2015-09-20 11:58:38 UTC
(In reply to Fabien Bourigault from comment #6)
> I'm writing a tool to get packageing errors. At a first look there is not so
> many errors and I looked at the qt4 bug report you did on Arch Linux bug
> tracker and the comment in the duplicate issue is that it's too hard to
> split the package because upstream don't care. I know other distro did the
> split but to fit the KISS philosophy is to contribute upstream to make the
> split easier.
> 
> As you can see the qt5 package have tools in a separate package because
> upstream make it possible.
> 
> So we will need to contribute upstream to make the split easier.

So it seems you're going to work with the upstream for each application/package that causes the issue and open bug reports where appropriate. This is thus not a GNOME Software issue and I'm closing this report. Thanks for your work.