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 690381 - Move wayland backend to dynamically loadable library
Move wayland backend to dynamically loadable library
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-12-17 21:36 UTC by Darxus
Modified: 2013-01-09 10:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Darxus 2012-12-17 21:36:00 UTC 
This basically comes from ubuntu:  https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352 (comment 61).  

They're not willing to have their GTK+ package require having a Wayland package installed to be able to use GTK+ with X.  Which is apparently currently the case due to the Wayland backend being built into GDK.
Comment 1 Matthias Clasen 2013-01-06 01:30:02 UTC 
No
Comment 2 Darxus 2013-01-06 06:06:23 UTC 
Matthias, can you provide any additional thoughts on the matter?  How packaging should be handled or something.
Comment 3 Emmanuele Bassi (:ebassi) 2013-01-09 10:56:25 UTC 
(In reply to comment #2)
> Matthias, can you provide any additional thoughts on the matter?

run-time discovery of backends would be a massive change in the architecture of GDK, and it would still break binary compatibility: we have API that is compiled only if the dependencies are available, because it depends on platform symbols being available. in short: in order to *compile* GTK+, you need to have its dependencies installed and available.

> How packaging should be handled or something.

the way everything is packaged: by packaging and shipping its dependencies.